Re: [tycho-user] Target vs repository

[Daniel Burrell <daniel.burrell@xxxxxxxxx>]

Ok thanks so to summarise one compatible set might be

- use target entirely by referencing a...

- ...p2 repo I maintain.

- remove the “repositories” entry in the pom file as tycho will figure things out from the target file.

- publish and maintain any 3rd party stuff to the internal p2 repo (using eclipse epr or bnd tools or similar).

Thanks for clarifying.

Dan

On Thu, 1 Mar 2018 at 12:35, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Hi,

On Thu, Mar 1, 2018 at 1:28 PM, Daniel Burrell <daniel.burrell@xxxxxxxxx> wrote:

So why would do both? 

In my opinion, you should avoid doing both a stick to .target as much as possible.

How should third party bundle artefacts be referenced and where should they be located and why?

- should it be made available by adding a reference to the p2 repository containing the artefact to the target platform?

Eclipse Orbit or JBoss Tools for examples do have a dedicated build to "osgi-ify" and "p2-ify" 3rd party libs which aren't already usable by p2. With this approach, the advantage is that everything becomes regular p2 artifacts that you can put in the .target file; and the drawback is that you have to build a separate "3rd-party" repository containing all such libs prior to build your own code.

HTH

--

Mickael Istria

Eclipse IDE developer, at Red Hat Developers community

Elected Committer Representative at the Eclipse Foundation board of directors

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user