[jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Oliver Lietz (Jira)

     [ https://issues.apache.org/jira/browse/SLING-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-788.
------------------------------------

    Resolution: Won't Fix

It seems there is no need for this feature anymore, therefore closing this bug.

> Provide /etc/cron.d/ style approach to scripting timed events
> -------------------------------------------------------------
>
>                 Key: SLING-788
>                 URL: https://issues.apache.org/jira/browse/SLING-788
>             Project: Sling
>          Issue Type: New Feature
>          Components: Commons
>            Reporter: Lars Trieloff
>
> I would like to be able to script scheduled events in an easy fashion that works just like the /etc/cron.d/ directory on my Linux server: I put a shell script into /etc/cron.d/daily and it will get executed once a day. In Sling terms this would mean having a node that takes nt:file scripts in any scripting language supported by sling that is executed on hourly, daily, weekly, monthly basis.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Bertrand Delacretaz
Hi,

On Fri, Sep 25, 2009 at 11:12 AM, Carsten Ziegeler (JIRA)
<[hidden email]> wrote:
> ...Carsten Ziegeler resolved SLING-788.
> ------------------------------------
>
>    Resolution: Won't Fix
>
> It seems there is no need for this feature anymore, therefore closing this bug....

Can't we keep such issues open, with "Issue Type = wish" ?

When discussed, several folks agreed that it's a good idea, we just
don't have time to implement it now.

-Bertrand

Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Felix Meschberger-2
Hi,

Bertrand Delacretaz schrieb:

> Hi,
>
> On Fri, Sep 25, 2009 at 11:12 AM, Carsten Ziegeler (JIRA)
> <[hidden email]> wrote:
>> ...Carsten Ziegeler resolved SLING-788.
>> ------------------------------------
>>
>>    Resolution: Won't Fix
>>
>> It seems there is no need for this feature anymore, therefore closing this bug....
>
> Can't we keep such issues open, with "Issue Type = wish" ?
>
> When discussed, several folks agreed that it's a good idea, we just
> don't have time to implement it now.

Sounds like a reasonable proposal to me. The same would then apply to
SLING-478 (Web Forms2), but probably not to SLING-255 (there is probably
no value with using Tika just for this case)

Regards
Felix

Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Carsten Ziegeler
Felix Meschberger wrote:

> Hi,
>
> Bertrand Delacretaz schrieb:
>> Hi,
>>
>> On Fri, Sep 25, 2009 at 11:12 AM, Carsten Ziegeler (JIRA)
>> <[hidden email]> wrote:
>>> ...Carsten Ziegeler resolved SLING-788.
>>> ------------------------------------
>>>
>>>    Resolution: Won't Fix
>>>
>>> It seems there is no need for this feature anymore, therefore closing this bug....
>> Can't we keep such issues open, with "Issue Type = wish" ?
>>
>> When discussed, several folks agreed that it's a good idea, we just
>> don't have time to implement it now.
>
> Sounds like a reasonable proposal to me. The same would then apply to
> SLING-478 (Web Forms2), but probably not to SLING-255 (there is probably
> no value with using Tika just for this case)
>
Now, if noone is working on this stuff and if there is no patch, I
really doubt that
this issue will ever get done - and if someone comes up with something,
the issue can easily be reopened.

But I agree that we can also just change them to "wish" if people think
that this is the better way of handling this. But I really fear that we
end up with a lot of wishes over time :)

Carsten


--
Carsten Ziegeler
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Bertrand Delacretaz
Hi,

On Fri, Sep 25, 2009 at 12:01 PM, Carsten Ziegeler <[hidden email]> wrote:
> ...But I agree that we can also just change them to "wish" if people think
> that this is the better way of handling this. But I really fear that we
> end up with a lot of wishes over time :)...

I don't think that's a problem - it also helps to show what we think
can be improved in Sling.
-Bertrand

Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Jukka Zitting
Hi,

On Fri, Sep 25, 2009 at 1:16 PM, Bertrand Delacretaz
<[hidden email]> wrote:
> I don't think that's a problem - it also helps to show what we think
> can be improved in Sling.

Yeah, one of the key purposes of an issue tracker is to keep track of
issues even when nobody is actively working on them.

So, as long as there's a valid use case for a requested feature, and
it's neither already implemented in some other way nor outside the
scope of the project, I'd keep the issue open as a reminder.

BR,

Jukka Zitting

Reply | Threaded
Open this post in threaded view
|

Re: [jira] Resolved: (SLING-788) Provide /etc/cron.d/ style approach to scripting timed events

Alexander Klimetschek
On Fri, Sep 25, 2009 at 13:21, Jukka Zitting <[hidden email]> wrote:

> On Fri, Sep 25, 2009 at 1:16 PM, Bertrand Delacretaz
> <[hidden email]> wrote:
>> I don't think that's a problem - it also helps to show what we think
>> can be improved in Sling.
>
> Yeah, one of the key purposes of an issue tracker is to keep track of
> issues even when nobody is actively working on them.
>
> So, as long as there's a valid use case for a requested feature, and
> it's neither already implemented in some other way nor outside the
> scope of the project, I'd keep the issue open as a reminder.

ACK.

Regards,
Alex

--
Alexander Klimetschek
[hidden email]