Re: [tycho-user] Deploying P2 Metadata to Artifactory

[Timo Rohrberg <rti.init@xxxxxxxxxxxxxx>]

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?

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?

Thanks again for any comments.

Regards
Timo


2011/10/27 Igor Fedorenko <igor@xxxxxxxxxxxxxx>:
> Tycho cannot use remote maven repositories to share binary (p2)
> artifacts between builds. There are some semi-working solutions that let
> you use plain http server to publish p2 repositories built with Tycho.
> This is how we build m2e and m2e extensions (m2e-tycho, m2e-wtp, etc).
>
> --
> Regards,
> Igor
>
> On 11-10-27 10:30 AM, Timo Rohrberg wrote:
>>
>> Hello everybody,
>>
>> we somehow have problems with deploying and consuming Eclipse
>> Plugins/Features built with Tycho 0.13.0 to/from our central JFrog
>> Artifactory 2.3.1. Building is done by Jenkins 1.414 by executing the
>> appropriate Tycho plugins. When building an Eclipse feature using the
>> attached pom_1.xml for example, Jenkins correctly deploys the
>> resulting JAR-file to its local Maven Repository, and to the central
>> Maven Artifactory (JFrog). The feature can then be consumed by other
>> projects (e.g. an Eclipse feature using the attached pom_2.xml) from
>> Jenkin's local Maven Repository. Once we delete it there, Tycho no
>> longer can resolve the dependency.
>>
>> We have only one idea of what is going wrong: Within the local Maven
>> Repository there is a folder named ".meta" in which all available
>> bundles are listed in a "p2-artifacts.properties" file. As long as the
>> corresponding artifact is available in the local Maven Repository
>> everything is fine. Once it's deleted there, Tycho also removes its
>> corresponding entry in that file and can no longer resolve it from the
>> central Artifactory.
>>
>> Somehow it seems that the central Artifactory is not p2 aware or Tycho
>> did not correctly deploy p2 metadata.
>>
>> Do you have any hints, suggestions or comments on how to solve that issue?
>>
>> Thanks a lot.
>>
>> Regards
>> Timo
>>
>>
>>
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
>