Hi,
Since version 2.5.4, maven-bundle-plugin has changed its behaviour and
using the ipojo-maven-plugin with it doesn't work anymore.
I'm using maven 3.3.3 and the settings that work fine with mbp 2.5.3
fail using 2.5.4.
org.apache.maven.plugin.MojoExecutionException: The input file
/home/git/babylon/babylon-rest/target/classes is not a Jar file
at
org.apache.felix.ipojo.plugin.ManipulatorMojo.execute(ManipulatorMojo.java:277)
~[na:na]
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
~[maven-core-3.3.3.jar:3.3.3]
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
~[maven-core-3.3.3.jar:3.3.3]
This is due to project.getArtifact().getFile() now returning the
directory target/classes rather than a valid JAR file (in
ManipulatorMojo). I suppose this is set by mbp.
The IPojo manipulator is able to "pojoize" directories directly but
expects a JAR file instead and thus fails.
Does anyone know if it is possible to configure the maven-bundle-plugin
to keep its old behaviour? What is the reason for the change, and
against which component should I open a bug? :-)
I will test using the staged mbp 3.0.0 to see if the bug is still there
in case a quick fix is possible before the release.
Thanks,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
