[
https://issues.apache.org/jira/browse/FELIX-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813863#comment-13813863
]
Stuart McCulloch commented on FELIX-4303:
-----------------------------------------
Also note that bnd will consider OSGi manifests of bundles on the classpath
when generating metadata - but these won't affect the Java compiler since it is
not OSGi aware. To enforce OSGi rules during compilation Tycho swaps in the
Eclipse compiler (ecj) and uses target platforms.
> The OSGI manifest of bundle dependencies should be considered within the
> compile and test classpath
> ----------------------------------------------------------------------------------------------------
>
> Key: FELIX-4303
> URL: https://issues.apache.org/jira/browse/FELIX-4303
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.4.0
> Reporter: Konrad Windszus
>
> Currently it is no difference whether I include a dependency with type=jar or
> type=bundle. In both cases the JAR is added to the classpath and the OSGi
> manifest is not considered for the Maven compile and test classpath. Would it
> be possible to let Maven already consider the export-packages section of the
> manifest within its own classpaths?
> I don't know whether Maven already supports that because the
> org.apache.maven.artifact.handler.ArtifactHandler doesn't give you the
> possibility to define your own classloader.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
