| Re: [cbi-dev] cbi-dev Digest, Vol 3, Issue 4 |
|
Hi Herbert, If you would, when you raise the ticket(s), please add them as dependencies for this ticket: Bug 371236 or let me know it and I'll add it. 371236 aggregates tickets to a single ticket tracking overall LTS readiness. In addition to the ticket(s) to track adding the dependencies to Orbit, I'm guessing there will be a ticket against stardust to modify the build to use them. Regarding your question about 2, there are some Orbit committers on this list, they may be able to comment on precedent for third party software with modifications. Regarding 1, I suspect both maven.eclipse.org and Orbit are necessary until such a day that all projects are using Maven/Nexus and there are no technical blockers preventing consolidation. Andrew On 02/09/2012 08:16 AM, Herbert.Neureiter@xxxxxxxxxxx wrote: Thanks for pointing this out, Wayne. I had expected so. Concerning the technical requirements, it is as Igor wrote: The p2 repositories and tycho will help us, but only for plugin builds. A large part of our build process is a "classical" Maven/Ivy build that requires single dependencies to be described in a POM and available from a Maven repository. An example for this would be https://dev.eclipse.org/ipzilla/show_bug.cgi?id=6228 : The approved library would need to be published into the Nexus repository with proper POM file. I notice a similar topic was already discussed: http://dev.eclipse.org/mhonarc/lists/dash-dev/msg01104.html . However we did not find the content mentioned there, yet. So, to summarize, we will create bugs against Dash/Maven for the inclusion of all dependencies from Orbit that we currently have approved CQs for. Given the large number of dependencies I'd rather create one "bulk ticket" for the list of currently approved CQs and then single bugs for later updates. What is less clear to me is how to proceed with approved dependencies that currently are NOT in Orbit. This question comes in two flavors: 1) Libraries that were approved for reuse as is, be it via a PB or regular CQ (examples would be https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5318 or https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5503 ). In this case I would see two options: - either they could be provided in to the repository "central" on http://maven.eclipse.org/nexus/index.html#welcome (I assume this is intended for approved dependencies that are available on maven central, but as discussed within eclipse needs to be consumed via maven.eclipse.org ) Would this be triggered via a bug report against das/maven, too ? - or add these to orbit and proceed as described above. 2) Libraries that are approved for reuse with modifications (subset). An example would be https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5561 . In this case I am not entirely sure what the process and distribution of responsibilities would be to get the modified binaries made available via maven.eclipse.org. Would the standard process be via an Orbit contribution or are there other ways to address this? Best Regards Herbert Message: 1 Date: Wed, 08 Feb 2012 11:59:41 -0500 From: Wayne Beaton <wayne@xxxxxxxxxxx> To: cbi-dev@xxxxxxxxxxx Subject: Re: [cbi-dev] How to consume eclipse orbit libraries in maven build Message-ID: <4F32A9FD.9050807@xxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Eclipse project builds must resolve third-party dependencies through eclipse.org sources. Sorry, but obtaining dependencies for distributable Eclipse content from Maven central is a no-no. maven.eclipse.org is still a work-in-progress. If improvements are needed, please open bugs against Dash/Maven. I'm hopeful that our new release engineer will be able to spend some cycles helping the Dash committers make maven.eclipse.org do what we need it to do. Wayne _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cbi-dev |
