[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[tycho-user] Nexus-hosted p2 repositories
|
Hello all,
I've been very pleased with how the Nexus Unzip Plugin has been working
out for sharing a p2 repository our PDE built dependencies. Once set up,
the virtual repository URL works well for resolving Tycho dependencies.
I would now like to use the Nexus P2 Repository Plugin to allow
rebuilding individual Tycho-built plugins while resolving their
dependencies from bundles previously deployed to Nexus through Tycho.
However, I'm seeing some odd behaviour when I point to the
<nexus>/<repo>/.meta/p2 repository URL, which does contain my artifacts
in p2 repository format on the file system.
When I include this repository in the eclipse-plugin's POM directly, I
see what I would expect in the log:
[DEBUG] Added p2 repository my_repo (http://<nexus>/<repo>/.meta/p2)
However, when I add it to its ancestor POM this Nexus-hosted p2
repository is not listed as "added" in the log. The build then fails due
to missing dependencies. Other non-Nexus-hosted p2 repository URLs are
inherited fine from this (grand)parent POM, but this <repository> is
ignored. I have also tried creating a p2 repository proxy that points to
the .meta/p2 URL just to see if it would help, but the results are the same.
Would anyone have an idea why this may be happening?
Thanks a lot in advance,
Irene