[jira] [Commented] (FELIX-4303) The OSGI manifest of bundle dependencies should be considered within the compile and test classpath

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus commented on FELIX-4303:
----------------------------------------

It seems that the takari-lifecycle-plugin would support evaluating the manifest information (http://takari.io/book/40-lifecycle.html#enforcing-dependency-usage-during-compilation). Did not yet try that though.

> 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.3.4#6332)