[ https://issues.apache.org/jira/browse/FELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568098#action_12568098 ]
Stefano Lenzi commented on FELIX-487: ------------------------------------- I think that we have two options: 1 - Compile the framework with JDK 1.3.1 2 - Use some kind of preprocessor in order to compile custom code I think that the best solution is the 1st on because the former will require to release also different binaries depending on the platform and it will use "ugly" preprocessing like //#ifdef or //[ifdef]. Also I wondering how to *reset* the bootclasspath to the JVM default from inner project if they don't want to be org.osgi.foundation compatible. > 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.diff.r620530.patch > > > As we discussed on the mailing list, see thread at > http://www.mail-archive.com/dev@felix.apache.org/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.