felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-2869) Support for custom handling of directories
Date Mon, 19 Mar 2012 13:49:38 GMT

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

Guillaume Nodet updated FELIX-2869:

    Issue Type: Improvement  (was: Bug)
       Summary: Support for custom handling of directories  (was: FileInstall handling of
directories in the watched directory is not powerful enough)
> Support for custom handling of directories
> ------------------------------------------
>                 Key: FELIX-2869
>                 URL: https://issues.apache.org/jira/browse/FELIX-2869
>             Project: Felix
>          Issue Type: Improvement
>          Components: File Install
>    Affects Versions: fileinstall-3.1.4
>            Reporter: Alasdair Nottingham
> In the Aries project we have an ArtifactInstaller for installing our flavour of OSGi
applications. We can tell something in the watched directory is an OSGi application because
it ends with .eba. We do not care if it is a directory, or an archive, we would cope with
both. However we do need it to end in .eba
> The problem is that in the directory case the canHandle method and the install method
are passed different things. canHandle is passed a jared up copy of the directory with a .jar
extension. install is passed the directory in the watched dir. This breaks my scanning algorithm,
which has to be based on extension, as the file has a .jar. I can't even update it to accept
a .eba.jar because I only want to support that in the case where file install has jared it
up from a directory, not any .eba.jar, but I can't tell this.
> Another concern is if my ArtifactInstaller can cope with a jar, but not a directory then
the current approach would call my install method and be broken.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message