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

Tobias Bocanegra commented on JCRVLT-241:
-----------------------------------------

(didn't know about the .bundle type. sounds wrong to me to create such 
artifacts. a jar is a jar is a jar :-)

the import package is particularly used to specify the runtime dependency on 
java packages. since the package build/compile isn't needed for packages, it 
makes no sense to use those as dependency.

also, in the normal OSGi or J2EE environment where the packages are usually 
used, it is wrong (or not very optimal) to use compile-scope dependencies, as 
they over populate the classpath with the transitive dependencies.

https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

> Goal analyze-classes: Dependencies with type "bundle" not correctly considered
> ------------------------------------------------------------------------------
>
>                 Key: JCRVLT-241
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-241
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: package maven plugin
>    Affects Versions: package-maven-plugin-1.0.0
>            Reporter: Konrad Windszus
>
> The goal {{analyze-classes}} only evaluates dependencies of type "jar" 
> (https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/trunk/src/main/java/org/apache/jackrabbit/filevault/maven/packaging/ImportPackageBuilder.java#L150).
>  This is not correct as even type "bundle" (being supported through the 
> {{maven-bundle-plugin}}) contains OSGi bundles.
> That leads to the fact that the version cannot be determined for dependencies 
> towards packages from bundle type dependencies.
> Also I am wondering why only dependencies with scope "provided" or "runtime" 
> should be considered. Very often dependencies are having the default scope 
> only (i.e. compile) which should not cause any issues.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to