[FELIX-5062] maven-bundle-plugin includes tests dependencies in package analysis

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-bundle-plugin-3.0.0
• Fix Version/s: maven-bundle-plugin-3.0.1
• Component/s: Maven Bundle Plugin
• Assignee: Carsten Ziegeler
• Reporter: Radu Cotescu
• Created: 05/Oct/15 09:05
• Updated: 19/Dec/19 17:37
• Resolved: 27/Oct/15 07:13

Description

It appears that version 3.0.0 of the maven-bundle-plugin includes test dependencies in its package analysis:

[INFO] --- maven-bundle-plugin:3.0.0:bundle (default-bundle) @ org.apache.sling.scripting.javascript ---
[WARNING] Bundle org.apache.sling:org.apache.sling.scripting.javascript:bundle:2.0.25-SNAPSHOT : Split package, multiple jars provide the same package:org/mozilla/javascript/debug
Use Import/Export Package directive -split-package:=(merge-first|merge-last|error|first) to get rid of this warning
Package found in   [Jar:rhino, Jar:js]
Class path         [Jar:., Jar:org.apache.sling.api, Jar:org.apache.sling.scripting.api, Jar:org.apache.sling.scripting.core, Jar:org.apache.sling.jcr.resource, Jar:org.apache.sling.commons.classloader, Jar:org.apache.sling.commons.json, Jar:org.apache.sling.commons.osgi, Jar:org.osgi.core, Jar:org.osgi.compendium, Jar:jcr, Jar:servlet-api, Jar:org.apache.felix.scr.annotations, Jar:rhino, Jar:slf4j-api, Jar:commons-collections, Jar:commons-io, Jar:org.apache.sling.commons.testing, Jar:org.apache.sling.jcr.api, Jar:jackrabbit-api, Jar:jackrabbit-jcr-commons, Jar:jackrabbit-core, Jar:concurrent, Jar:commons-dbcp, Jar:commons-pool, Jar:jackrabbit-spi-commons, Jar:jackrabbit-spi, Jar:tika-parsers, Jar:tika-core, Jar:commons-compress, Jar:pdfbox, Jar:fontbox, Jar:jempbox, Jar:bcmail-jdk15, Jar:bcprov-jdk15, Jar:poi, Jar:poi-scratchpad, Jar:poi-ooxml, Jar:poi-ooxml-schemas, Jar:xmlbeans, Jar:dom4j, Jar:geronimo-stax-api_1.0_spec, Jar:tagsoup, Jar:asm, Jar:metadata-extractor, Jar:boilerpipe, Jar:rome, Jar:jdom, Jar:netcdf, Jar:jcl-over-slf4j, Jar:lucene-core, Jar:derby, Jar:org.apache.sling.adapter, Jar:js, Jar:commons-httpclient, Jar:commons-codec, Jar:slf4j-simple, Jar:junit, Jar:hamcrest-core, Jar:jmock-junit4, Jar:jmock, Jar:hamcrest-library, Jar:junit-dep, Jar:powermock-module-junit4, Jar:powermock-module-junit4-common, Jar:powermock-core, Jar:javassist, Jar:powermock-reflect, Jar:objenesis, Jar:powermock-api-mockito, Jar:mockito-all, Jar:powermock-api-support, Jar:bndlib]

In this case js.jar is a transitive dependency of a testing dependency:

<dependency>
    <groupId>org.apache.sling</groupId>
    <artifactId>org.apache.sling.commons.testing</artifactId>
    <version>2.0.16</version>
    <scope>test</scope>
</dependency>

For more details check the pom from https://github.com/apache/sling/blob/0faf720a105fb26ba6d02c476f9674830b06262b/bundles/scripting/javascript/pom.xml.

Issue Links

• relates to: SLING-5080 org.apache.sling.scripting.javascript fails baseline check with maven-bundle-plugin 3.0.0
• relates to: SLING-5196 missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl