[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] tycho eclipe-plugin and m2e: where to specify dependencies
|
The purpose of Tycho is to build Eclipse PDE projects outside of Eclipse
and that's why it strictly following PDE project configuration
practices. It's also useful to deliver Eclipse specific artifacts like
P2 update sites from a Maven build.
Cheers,
Rafał
On 10/14/2012 06:39 PM, Steinar Bang wrote:
The tycho eclipse plugin on the eclipse wiki
http://wiki.eclipse.org/Tycho/Packaging_Types#eclipse-plugin
says:
"Since Tycho uses OSGi bundle manifest to determine project
dependencies, pom.xml file should NOT contain <dependency> section,
and any dependencies inherited from parent project will be ignored by
the build."
This feels kind of wrong to me. One big pro with eclipse is how
dependencies are handled uniformly.
And after learning how to fix problems with dependencies in a complex
eclipse build, here I suddenly get to a place where there is a java
project, but dependencies aren't in the POM but are instead in a
different form in a manifest file (I assume that's where they are...?).
In addition this project will not see any of the inherited
dependencies.
Why couldn't the dependencies have been in the POM in a normal fashion,
and m2e or the bundle plugin could have generated the manifest?
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
