[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] P2 repository ignored with Java 11?
|
Hi, are you use you don’t accidentally use maven 3.6.1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=546463
---
Gesendet von Boxer | http://getboxer.com
Am 27. Mai 2019 um 19:51:13 MESZ schrieb Axel Guckelsberger <info@xxxxxxxx>:
Hi all,
I am currently migrating a project from Java 8 to Java 11. The Jenkins
jobs work based on that in addition to the common target definition
there are additional p2 repositories consumed for materialising the
target platform. So while the parent POM contributes the target platform
the component's POM adds one or several repository entries like this:
<repositories>
<repository>
<id>some-dependency</id>
<url>file://${dependency.repository}</url>
<layout>p2</layout>
</repository>
</repositories>
The idea behind that is that all jobs share the target platform, but
still can depend on each other. For example component C needs components
A + B and so on.
When using Java 8 the output before "[INFO] Resolving dependencies of
MavenProject:" was:
> Adding repository
> file:/...jenkins/jobs/.../branches/master/lastSuccessful/...dependency-component.build/target/repository
Now with Java 11 this step is unfortunately skipped which leads to that
the dependency can not be resolved.
Any idea what could cause this different behaviour and/or how a
workaround could look like?
I am using Tycho 1.4.0.
TIA
Axel
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/tycho-user
