Re: snappy-java mh-buildable with libmaven-bundle-plugin-java 2.3.4 but not 2.3.5.
On Fri, 4 Nov 2011 14:19:53 +0900, Charles Plessy <plessy@debian.org>
wrote:
> Dear all,
Hi Charles,
> noticing that libmaven-bundle-plugin-java is still at version 2.3.4 in
> Wheezy,
> I downgraded and the package built fine. However, it refuses to build
with
> 2.3.5. If I edit the pom.xml file to replace 2.3.4 by 2.3.5, then
mh_make
> successfully prepared a Debian source package, but build fails with the
> following error.
>
> (Regression tests and JavaDoc disabled)
[...]
> java.lang.NoSuchMethodError:
>
aQute.lib.osgi.Processor.printClauses(Ljava/util/Map;Z)Ljava/lang/String;
> at
>
org.apache.felix.bundleplugin.BundlePlugin.mergeMavenManifest(BundlePlugin.java:701)
> at
>
org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:481)
> at
>
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:343)
> at
>
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:260)
> at
>
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:251)
> at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at org.debian.maven.Wrapper.main(Wrapper.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
// with my maven-bundle-plugin hat on...
I've already saw this exception "java.lang.NoSuchMethodError:
aQute.lib.osgi.Processor.printClauses" when updating maven-bundle-plugin
from 2.3.4 to 2.3.5.
That's why maven-bundle-plugin Depends on "bnd (>= 1.44.0)" but maybe
there is something wrong with this...
Could you please provide a .dsc file so I can debug this locally ?
Cheers,
--
Damien
Reply to: