[
https://issues.apache.org/jira/browse/FELIX-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813862#comment-13813862
]
Stuart McCulloch commented on FELIX-4303:
-----------------------------------------
This is somewhat outside of the scope of the bundleplugin - it's primary job is
generation of OSGi metadata (using the bnd library) rather than controlling the
overall compilation classpath of the project. You might want to look at Maven
Tycho (http://eclipse.org/tycho/) which does provide a compilation classpath
with strict OSGi rules (and has to hook into Maven at the low-level to do so).
> 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)
