[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] Unifying p2 & maven
|
Hi Alex,
I agree with you. There are some things that don't make sense to
distribute as a Maven repository. Others however make good sense as they
are consumed outside of Eclipse.
Related, is anyone here using this?:
http://wiki.eclipse.org/Eclipse_b3/aggregator/manual#Creating_a_Maven-conformant_p2_repo
Andrew
On 12/04/2012 02:29 PM, Aleksandar Kurtakov wrote:
----- Original Message -----
From: "Andrew Ross" <andrew.ross@xxxxxxxxxxx>
To: "Common-build Developers discussion" <cbi-dev@xxxxxxxxxxx>
Sent: Tuesday, December 4, 2012 8:55:00 PM
Subject: [cbi-dev] Unifying p2 & maven
Hi Everyone,
We're getting very close to cutting over the Eclipse platform to CBI.
There will be a bit of cleanup stuff to be ready for Juno SR2 to
cut-over as well.
I'd like to get people thinking about our next big challenge...
figuring
out and implementing a good solution for maven.eclipse.org.
Please read this for background & some thoughts I have on the matter:
http://42aross.wordpress.com/2012/12/04/my-take-on-mavenp2-unification-at-eclipse/
I'd be grateful for some feedback to help make sure I haven't
overlooked
something important and to assist us to develop the right solution.
Hi Andrew,
Technically speaking with current tools it makes no sense to ship things as Maven repo for one big reason:
* Our pom.xml files contain no information about dependencies - we manage them trough manifest files which makes way more sense as it's more flexible and controllable compared to maven dependencies management.
As such even if we push all the bundles in a maven repository it will be practically unusable as there would be no way plain maven build(no tycho) can know that e.g. org.eclipse.pde.ui requires org.eclipse.team.core. And if people use tycho they can already read the p2 repos we have. Not to mention problems that will arise if one tries to map import-package to dependencies and so on.
With that said - let's have maven.eclipse.org be a normal maven repo for eclipse.org that doesn't use manifest first approach. For the rest of us that use manifest first it makes no sense to even try supporting plain maven builds
Alexander Kurtakov
Red Hat Eclipse team
Thanks in advance,
Andrew
