On 03/15/2012 06:51 AM, Max Rydahl Andersen wrote:
> Right, I forget you're downstream from JBoss Tools Core. This usecase is
> being considered here:
>
note: when we start splitting up our giant repo into smaller parts many more will be
downstream of "core" so this challenge
is not limited to the likes of switchyard.
Its actually already a problem today if you just want to develop on the mvn plugins - you
also need to check out the code for everything else to build it.
/max
Not true.
svn co
http://svn.jboss.org/repos/jbosstools/trunk/build/
svn co
http://svn.jboss.org/repos/jbosstools/trunk/maven/
cd maven; mvn clean install
-Plocal.site,jbosstools-nightly-staging-composite
-Dlocal.site=file://path/to/locally/unzipped/targetplatform/
In that mode, you'll only need the sources for the maven plugins, and
the rest will be resolved from upstream trunk composite staging site.
You know the parent pom includes instructions for how to build against
various different upstream bits, right?
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com