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

Karl Pauls resolved FELIX-5718.
-------------------------------
    Resolution: Fixed

Done in r1812580.

They way this works is pretty simple. All it does is to detect the available 
modules in the current layer (the one that loaded Felix or boot when in the 
unnamed module) and then make a property available for each module that looks 
like: 

felix.detect.jpms.<module-name>

With that, we should be able to pick up on those property when calculating the 
export package list. 

Furthermore, I added support for picking up properties from the default 
properties using a new prefix "felix.jpms.". I think that will be enough to 
lift module package definitions from the default properties. 



> Autodetect modules available
> ----------------------------
>
>                 Key: FELIX-5718
>                 URL: https://issues.apache.org/jira/browse/FELIX-5718
>             Project: Felix
>          Issue Type: Sub-task
>          Components: Framework
>    Affects Versions: framework-5.6.8
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>             Fix For: framework-5.6.10
>
>
> Following [~nbartlett]'s lead (e.g., [0]) it looks like what we have todo is 
> to detect modules that are available and provide a way to expose them via the 
> system bundle. 
> [0] 
> https://github.com/njbartlett/osgi_jigsaw/blob/master/nbartlett-jigsaw-osgi/src/nbartlett.jigsaw_osgi/nbartlett/osgi_jigsaw/Main.java



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to