felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Kriens (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-530) Separate DirectoryWatch function from action
Date Mon, 02 Jun 2008 07:37:45 GMT

    [ https://issues.apache.org/jira/browse/FELIX-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601542#action_12601542

Peter Kriens commented on FELIX-530:

Well, the class is quite small and easy to copy and modify. I am not sure the extra complexity

to make it generic weighs up against the added genericity. 

> Separate DirectoryWatch function from action
> --------------------------------------------
>                 Key: FELIX-530
>                 URL: https://issues.apache.org/jira/browse/FELIX-530
>             Project: Felix
>          Issue Type: New Feature
>          Components: File Install
>            Reporter: Toni Menzel
> I would like to pull the actions out of the DirectoryWatcher class.
> Instead, this class just detect/tracks changes like it currently does and calls an appropriate
action contributed via extender pattern.
> This way, other bundles can 
> 1. contribute functionality like handling other stuff than final bundles and .cfg files.
> 2. replace the current behavior
> 3. DirectoryWatcher gets slicker / easier to maintain
> The current two behaviors (install/update/remove on .jar Bundles and .cfg) could be installed
in the activator by default (just like felix.shell does with its commands)

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

View raw message