You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2017/12/01 13:42:00 UTC

[jira] [Updated] (JCRVLT-241) Goal analyze-classes: Dependencies with type "bundle" not correctly considered

     [ https://issues.apache.org/jira/browse/JCRVLT-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Bocanegra updated JCRVLT-241:
------------------------------------
       Resolution: Fixed
    Fix Version/s: package-maven-plugin-1.0.1
           Status: Resolved  (was: Patch Available)

fixed in r1816853

> 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
>             Fix For: package-maven-plugin-1.0.1
>
>
> 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)