Re: [tycho-user] having Maven provision the eclipse target platform dire

[Neil Corbet <neil.corbet@xxxxxxxxx>]

Also, I do organize some of my 3rd party plugins ( the ones I want to add to my target ) into features. I have a project setup to create a p2 repository out of these feature groups. I think, move this repo to an instance of tomcat ( or whatever ) and then proxy that site through Nexus. I can then "shop" for 3rd party features for my target that way.

In order to build the p2 repository, I utilize the 3rd Party repo in Nexus to upload the 3rd party plugins individually. I then p2 enabled the 3rd party repo. This way, when tycho assembles the p2 repo it can download those plugins from nexus. This may seem clunky at first, but it has really started to flow better for us.

Another thing I do is I have multiple p2 proxies that I also group together using the Group feature in nexus. I can then just use that repo address in the repositories section of my pom. I can also add it as a mirror in my settings.xml.

Hope that helps.

Neil

On Thu, Jan 16, 2014 at 12:13 PM, Cohen, Tamar (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] <tamar.e.cohen@xxxxxxxx> wrote:

Ok and I see this only has the features, as Moritz wrote.  This won't work for our 3rd party plugins as they are not organized into features.

Sonatype support suggested I publish the artifacts to a hosted site repository in Nexus, but I'm a bit concerned if those will be aggregated into one p2 site or not.

I surely cannot be the only one trying to do this …

Tamar

On Jan 16, 2014, at 1:58 AM, Moritz Bechler <bechler@xxxxxxxx> wrote:

> Hi,
>
>>
>> We followed the steps on that page and set Nexus up to provision our p2
>> site; despite the fact that we have followed all the configurations
>> carefully and are attempting to hit the p2 site from our target
>> platform, it shows no content.  Is there an example?  Are there special
>> settings in tycho?  We're publishing all the p2 content, so for each
>> Eclipse artifact we build there is a p2artifacts.xml and p2metadata.xml
>> file and the contents look clean.  It seems like the aggregator is not
>> aggregating them?
>>
>> Thanks so much for any input, this is a key part of using Nexus for us!
>
> The nexus p2 plugin is indeed not aggregating the tycho generated P2
> data, but only what their generator produces from the JARs. So you will
> also have to enable the meta data generator on the repository (I'm not
> sure whether this will be useful, especially for features).
>
> We do have a customized plugin which in-cooperates the tycho generated
> descriptors - but I need to get approval for publishing first and have
> some time to get it ready for release.
>
> Also, note that you won't be able to pick individual plugins for the
> target platform using this repository layout, but only features and as
> Neil noted you have to disable categories to see any contents at all.
>
>
> with best regards
>
> Moritz
>
> --
> AgNO3 GmbH & Co. KG, Sitz Tübingen, Amtsgericht Stuttgart HRA 728731
> Persönlich haftend:
> Metagesellschaft mbH, Sitz Tübingen, Amtsgericht Stuttgart HRB 744820,
> Vertreten durch Joachim Keltsch
>

> _______________________________________________
> 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