[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [tycho-user] Resolve Maven plugin dependencies from target platform?
|
This is theoretically possible, but Tycho does not do this right now and
I am not aware of any attempts to implement this either.
I am not even sure you need/want to make this part of Tycho. What you
are looking for, basically, is Maven repository layout implementation
that is able to perform jar and pom (!) artifact lookup based on maven
artifactcoordinates. This is quite different from what Tycho does not
project dependencies.
The difficult part is, of course, figuring out how to represent OSGi
dependencies in Maven, but maybe you can get away by simply ignoring the
problem.
If you really need just couple of dependencies, however, it is probably
easier to manually publish the required artifacts to a Maven repository.
This is how we make equinox and jdt compiler available for Tycho [2].
[2]
http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-releng/pom.xml
--
Regards,
Igor
On 2014-11-06, 12:06, Andreas Sewe wrote:
Hi,
AFAIK, Tycho hooks into Maven's dependency resolution and, through some
system-scope dependency magic, makes Maven pick up project dependencies
as declared in the target platform.
Now, I wonder whether it's possible to also resolve a *Maven* plugin's
dependencies from the target platform?
Why would one want to do that? Well, in our build we use the
xtext-maven-plugin which requires a couple of plugin dependencies [1].
All these dependencies are readily available from our target platform.
However, I still have to hunt down the "equivalent" JARs on Maven
central and maintain their versions in the POM. Keeping this in sync is
not fun.
Hence, I am wondering whether Tycho could hook into Maven's dependency
resolution in such a way that plugin dependencies could also come from
the target platform?
Best wishes,
Andreas
[1]
<https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/plugins/org.eclipse.recommenders.stacktraces.model/pom.xml?id=v2.1.10#n44>