[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Deploying P2 Metadata to Artifactory
|
On 11-10-27 11:14 AM, Timo Rohrberg wrote:
Hello Igor,
thanks a lot for your quick reply. Do I get you right: It is NOT
possible to share build results betweeen subsequent Tycho builds via a
remote maven repository, neither a JFrog Artifactory based one nor a
Sonatype Nexus based one? If this is true, I wonder why it perfectly
works with the local Maven Repository. What's exactly the difference
between those two?
Tycho publishes some additional metadata to local repository, which
allows it to resolve dependencies installed locally by previous builds.
The same metadata cannot be used with remote repositories. TYCHO-335 has
some additional details.
https://issues.sonatype.org/browse/TYCHO-335
We also came up with the idea already to work around that problem by
publishing p2 repositories to a plain http server. But how can you
merge the results of two or more subsequent, but individual builds
each resulting in an own self-contained p2 repository? Both of them
contain an artifacts.jar and contents.jar which are almost impossible
to merge manually...
Could you please give me some hints about the mentioned workarounds
you are using to build your m2e, ... extensions?
This is why I said "semi-working solutions". For m2e we currently
manually maintain composite repository at the root of directory
structure as explain in [1]. It maybe possible to automate, but I have
not looked at this yet.
[1] http://wiki.eclipse.org/M2E_updatesite_and_gittags
--
Regards,
Igor
