Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Minutes: platform CBI build -- building Kepler

As Thanh and Paul stated, the jdt compiler that comes with a certain tycho version can be overridden in pom.xml but needs to be available in a public maven repo.
when we release tycho we usually deploy the corresponding jdt compiler to maven central [1] but this process is a little involved and may not be suitable if only the eclipse platform build needs the M4 build of jdt for now.

just to check - is there a hard dependency on the M4 compiler? otherwise I don't think it's worth the hassle.

as an alternative to maven central, you could deploy it to the nexus instance on eclipse.org but you would have to make sure this repo is in the parent pom so others can continue to build the eclipse platform out of the box. Not sure about the current state of http://maven.eclipse.org/nexus/  -- general visibility of all artifatcs there may introduce other unwanted side-effects, so if you go down this road, I think you should make sure you have a dedicated repository (group) only for the CBI build-time dependencies and reference this one only.

[1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/pom.xml#n94 

Jan




From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Mickael Istria
Sent: Donnerstag, 10. Januar 2013 08:45
To: cbi-dev@xxxxxxxxxxx
Subject: Re: [cbi-dev] Minutes: platform CBI build -- building Kepler

Hi,

I would recommend to push at least all "common" things on Nexus. It's very easy to set up (just add a distributionManagement in parent pom) and consume (just add the nexus repo to parent). It will help you to get the build more modular, less dependent on local Maven repository and way easier to consume.
Also, it would share the artifacts of CBI (a parent pom, some mojos?) with other project, making it more "common" than it is now.
FYI we started to put our parents, target-platforms, and custom plugins for JBoss Tools on Nexus about 6 months ago, and everything became easier for both maintainers and users. It's really worth it.
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


Back to the top