m2e by itself knows nothing about maven-bundle-plugin and pde, you need to have m2e-tycho to make it understand packaging=bundle. Also, as I already mentioned, current version of m2e-tycho does NOT support Embed-Dependency. This support lives on a branch [1] and waits for [2], [3] and [4] to be reviewed and accepted by respective project development teams.
[1] https://github.com/sonatype/m2eclipse-tycho/tree/mbp-embed-dependency [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=353442 [3] https://issues.apache.org/jira/browse/FELIX-3061 [4] https://github.com/bnd/bnd/pull/71 -- Regards, Igor On 11-08-27 9:01 PM, Benson Margulies wrote:
I've found, I think, a bug in the maven-bundle-plugin. In my particular case, it generated the correct manifest into target/classes/META-INF ... and then sticks a *different* manifest into the result jar. So I tried to work around this by avoiding the 'bundle' packaging. By using the 'manifest' goal and some jar plugin config, I succeeded in getting it to leave the right manifest in place. Unfortunately, I can't seem to persuade M2E to pay attention to the embedded jars in the resulting artifact. In fact, M2E seems to not recognize my project as a bundle at all. In eclipse, I get errors like: Bundle 'org.apache.maven.doxia.ide.dependencies' cannot be resolved _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
