[
https://issues.apache.org/jira/browse/FELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Lenzi updated FELIX-487:
--------------------------------
Attachment: pom.xml.r628634.patch
I have updated the patch in order to define a profile ee-foundation which set
up the bootclasspath of the compiler.
I don't know how the best way for allowing subproject to enable the profile.
My best idea for automatic activation of the profile is by a property like
ee=foundation ( we could later add other execution enviroment).
PRO:
Easy to implement
CONS:
We have to move the module tags from the packaging bundle under the new profile
but it could be dififcult for subproject in particular if not all the submodule
uses the bundle packaging. Also we have to change the build.xml
> Compile bundles using org.osgi.foundation classlibrary instead of the JVM
> installed on the developer
> ----------------------------------------------------------------------------------------------------
>
> Key: FELIX-487
> URL: https://issues.apache.org/jira/browse/FELIX-487
> Project: Felix
> Issue Type: Improvement
> Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3
> Reporter: Stefano Lenzi
> Assignee: Stefano Lenzi
> Attachments: pom.xml.r620789.patch, pom.xml.r628634.patch
>
>
> As we discussed on the mailing list, see thread at
> http://www.mail-archive.com/[email protected]/msg01728.html
> Now that org.osgi.foundation has been released we can modify the java
> compiler bootclasspath in order to compile using only the org.osgi.foundation
> classes.
> My idea is to add such feature to the parent POM of felix only for the bundle
> profile.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
