[ 
https://issues.apache.org/jira/browse/FELIX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569476#action_12569476
 ] 

Stefano Lenzi commented on FELIX-487:
-------------------------------------

Richard said:
> In the patch from where is the org/osgi/ee/1.0/foundation-1.0.jar artifact 
> coming? You specify a dependency on org.apache.felix/org.osgi.foundation, 
> but this is not the same artifact.
you are right I have mixed up maven-compiler-dependency and bootclasspath with 
artifact that I have installed on my m2 local repo. The right configuration for 
the maven-compiler-plugin will be:
            <configuration>
              <compilerArguments>
                
<bootclasspath>${settings.localRepository}/org/apache/felix/org.osgi.foundation/1.0.0/org.osgi.foundation-1.0.0.jar</bootclasspat
h>
              </compilerArguments>
            </configuration>
            <dependencies>
              <dependency>
                <groupId>org.apache.felix</groupId>
                <artifactId>org.osgi.foundation</artifactId>
                <version>1.0.0</version>
              </dependency>
            </dependencies>


Karl said:
>Well, we will have to address the BigDecimal issue one way or the other and 
>this patch doesn't help us with it as is. 
AFAIK the JRE try to load a class as soon as it finds the import statement if 
that it's the only to get around the BigDecimal is to deploy bundle with 
classifier which identify the Execution Enviroment(EE)

>I think the comment about reseting the bootclasspath from within a project is 
>the important one. In case there is a solution then this patch could 
>include disabling the foundation for the projects that need a higher profile.
We can add a set of parent pom each of which setup the maven-compiler-plugin 
with a particular bootclasspath. In this way will have:
pom/pom.xml
pom.ee.foundation/pom.xml (parent pom will be pom/pom.xml)
bundle which are able to compile with foundation will have parent pom set to 
"pom.ee.foundation/pom.xml"
bundle which are default bootclasspath have parent pom set to "pom/pom.xml"

WDYT?

(See http://www.mail-archive.com/[email protected]/msg03165.html for POM 
decorator pattern)

> 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
>
>
> 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.

Reply via email to