Hi,
I’ve got a Camel project which is to be deployed into servicemix as an
OSGi-bundle where I’ve embedded a couple of third-party jars in the bundle.
This works nicely.
However, the class path to these bundles is set in MANIFEST.MF which is not
generated until *after* tests are run if I do a
mvn clean package or similar, causing camel tests in the project to fail
waiting for unresolved dependencies.
I can work around this by adding an explicit generation of MANIFEST.MF to
felix-bundle-plugin configuration.
<executions>
<execution>
<id>bundle-manifest</id>
<phase>process-classes</phase>
<goals>
<goal>manifest</goal>
</goals>
</execution>
</executions>
However, Eclipse then complains about duplicate manifest executions: "Duplicate
manifest executions found. Please remove any explicitly defined manifest
executions in your pom.xml"
Maven has no complaints when running from the command line.
Should I just ignore this as FUD from Eclipse, or is there a more appropriate
way to achieve this, generate the MANIFEST.MF before running tests?
Best regards,
/Fredrik
--
Fredrik Jönsson, M.Sc.
System Architect
KTH Royal Institute of Technology
University Administration
IT-avdelningen
Drottning Kristinas väg 48, SE-100 44 Stockholm, Sweden
Phone: +46-8-790 66 03
Mobile: +46-73-595 66 03
E-mail: f...@kth.se
Web: https://www.kth.se/profile/fjo
Twitter: https://twitter.com/fredrikjn
LinkedIn: http://se.linkedin.com/in/fredrikjn
