[SLING-5080] org.apache.sling.scripting.javascript fails baseline check with maven-bundle-plugin 3.0.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting JavaScript 2.0.24
• Fix Version/s: Scripting JavaScript 2.0.26
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Robert Munteanu
• Created: 30/Sep/15 13:08
• Updated: 12/Oct/15 13:28
• Resolved: 05/Oct/15 09:11

Description

After updating the maven-bundle-plugin to 3.0.0 the mentioned module fails to build due to a baseline check. When compared to the 2.5.3 build output, I can see that

1. it complains about multiple org.mozilla.javascript.... split packages, e..g.

[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/serialize
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]

2. It thinks that org.mozilla.javascript should be exported with the 1.1.0 version instead of 1.0.0, due to multiple classes being added: ScriptOrFnNode, PropertyException, NotAFunctionException, Node$Jump, FunctionNode, ClassDefinitionException .

The first note might hold the key to understanding why the second one happens ; bnd might have changed the way it embeds/reexports classes and therefore triggers this problem

Issue Links

• is related to: FELIX-5062 maven-bundle-plugin includes tests dependencies in package analysis
• is related to: SLING-5079 Update to maven-bundle-plugin 3.0.0