Re: [cbi-dev] How to consume eclipse orbit libraries in maven build

[Andrew Ross <andrew.ross@xxxxxxxxxxx>]

Hi Herbert,

Welcome to the list.

I'd like to suggest using the LTS-Ready definition as a checklist:
http://wiki.eclipse.org/LTS/LTS_Ready

As you note, the lack of orbit content and other dependencies available through maven.eclipse.org is a lost opportunity.

On this topic, everyone, if Nexus could store compressed p2 repositories and Maven could push/pull them, would that cover our basic needs? Certainly it would satisfy our needs for pulling dependencies from an Eclipse Foundation controlled source and likely make dependency consumption more consistent over time as projects adopt this method.

If this is a good solution that covers our needs, clearly there's work to be done to make this vision come true.

I'll add this to the agenda for our next CBI meeting February 21st so we can discuss.

Andrew

On 02/08/2012 08:59 AM, Herbert.Neureiter@xxxxxxxxxxx wrote:

Hi All,

 

I am a committer on project  Stardust and we are currently working on the setup of the build process for our sources. Our build is heavily based on Ivy and Maven, hence we need to consume our dependencies via maven.

 

For the largest part of our dependencies we already have CQs in “approved” state  and especially we have got approval to reuse quite a bit of stuff from Orbit.

 

Looking at the documents http://wiki.eclipse.org/Common_Build_Infrastructure#Maven and http://wiki.eclipse.org/Maven we were hoping to find most of what we need in the “orbit” repository on http://maven.eclipse.org/nexus/index.html#view-repositories . Furthermore, we were hoping that we could consume approved dependencies available from Maven central in the “central” repository of http://maven.eclipse.org/nexus/index.html#view-repositories .

 

Is this how the repositories are intended to be used? It seems that currently the orbit repository is empty and the “central” repository does not provide most of what we need. What would be the process to get approved Orbit and “central” dependencies made available via the nexus repository?

 

As a side-note: It appears that we can get some of our requested dependencies only approved as Subsets by removing problematic content. ? If modifications to the original dependency are mandated for legal reasons, we will need a dedicated repository to hold the modified artifacts. I assume in these cases a good approach might be to contribute them to orbit where possible and then consume them via the Nexus repository?

 

Thanks for any help on how to proceed.

 

 

Regards

 

 

Herbert

 

-----------------------------------------------

 

Dr. Herbert Neureiter • Vice President Product Management Infinity Process Platform • Infinity • Global Technology • SunGard • Solmsstr. 18, 60486 Frankfurt am Main, Germany • Tel +49 69 70768 566 • Mobile +49 176 1111 0180 • herbert.neureiter@xxxxxxxxxxx • www.sungard.com

P Think before you print
CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you receive this e-mail in error, please notify the sender and delete this e-mail from your system.

SunGard Systeme GmbH * Registered: Frankfurt am Main, Handelsregister Frankfurt HRB 56839 * Geschäftsführer: Harold Finders, Christian U. Haas, Thorsten Heissel, Richard J. Obetz, Victoria E. Silbey