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

["Robert Munteanu (JIRA)" <ji...@apache.org>]

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

Robert Munteanu commented on SLING-5080:
----------------------------------------

See also [dev@felix: Split-package warnings from embedded jars |http://felix.markmail.org/thread/5pfl53ym7d4c7jxt]

> org.apache.sling.scripting.javascript fails baseline check with maven-bundle-plugin 3.0.0
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-5080
>                 URL: https://issues.apache.org/jira/browse/SLING-5080
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JavaScript 2.0.24
>            Reporter: Robert Munteanu
>            Assignee: Radu Cotescu
>             Fix For: Scripting JavaScript 2.0.26
>
>
> 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.
> {noformat}[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]{noformat}
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)