FYI, if you use hub [1], then the process for checking out Mickael's
topic branch / PR is simply:
$ cd jbosstools-target-platforms
$ git checkout
https://github.com/jbosstools/jbosstools-target-platforms/pull/37
[1]
http://hub.github.com/
Added bonus is that if you don't already have mistria or mickaelistria
[2] listed as a repo source, he'll be added automatically to your list
of remotes.
[2]
https://github.com/mickaelistria/jbosstools-target-platforms/tree/Kepler-SR2
After the above, the same steps apply:
$ cd jbosstools/multiple
$ mvn clean install -P \!multiple2repo
Cheers,
Nick
On 02/21/2014 11:52 AM, Mickael Istria wrote:
Hi all,
Here is a proposal for a new 4.32.0.Alpha1-SNAPSHOT target
platform:https://github.com/jbosstools/jbosstools-target-platforms/pull/37
It consists in the following changes:
* Move to Kepler SR2
** some projects are still using same version that we had for Kepler release (Orbit,
m2eclipse, TM, SWTBot)
** most projects have contributed a SR2 build
Please review this PR and yell if there is anything shocking. You can use the following
stuff to try to build build the TP locally and try out against your component.
Once this changed is pushed, CI jobs for branch 4.1.x will be updated to use it as
TARGET_PLATFORM_MAXIMUM.
Build target-platform:
$ cd jbosstools-target-platforms
$ git fetch mistria Kepler-SR2
$ git checkout FETCH_HEAD
$ cd jbosstools/multiple
$ mvn clean install -P \!multiple2repo
Try with just built target-platform:
$ cd /path/to/your/component
$ mvn clean verify -Dtpc.version=4.32.0.Alpha1-SNAPSHOT -Pmultiple.target
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com