On Fri, Apr 05, 2013 at 10:38:32AM -0400, Nick Boldt wrote: Just to clarify it uses the release TP for now. once Kepler updates with new Milestone/RC's it will move forward but we'll notifiy about it. This sounds wrong - alpha2 is what we just used for Alpha2 - you mean Beta1-SNAPSHOT, right ? /max

Project Leads: If you haven't already done so, please commit the following one-line change to your project's root pom (in master branch ONLY) so you're building w/ the latest JBoss Tools parent pom and so that your plugins/feature have "Beta1" in their name instead of "Alpha2". If you don't, Max will yell at you. Repeatedly. -- Not sure what to do? Here's a sample [0] - <version>4.1.0.Alpha2-SNAPSHOT</version> + <version>4.1.0.Beta1-SNAPSHOT</version> [0] https://github.com/jbosstools/jbosstools-jst/commit/d50e176f93c6c585a9319... I hope to see the nightly trunk site [1] only contain Beta1 bits soon. It currently has a lot of Alpha2 in it. [1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ Thanks! -------- Original Message -------- Subject: Please adopt the 4.1.0.Beta1-SNAPSHOT version of the JBT parent pom in your project's master branch's root pom.xml Date: Fri, 05 Apr 2013 10:38:32 -0400 From: Nick Boldt <nboldt(a)redhat.com&gt; To: jbosstools-dev(a)lists.jboss.org <jbosstools-dev(a)lists.jboss.org&gt; I've updated the parent pom in the master branch to version Beta1: -<version>4.1.0.Alpha2-SNAPSHOT</version> +<version>4.1.0.Beta1-SNAPSHOT</version> -<BUILD_ALIAS>Alpha2</BUILD_ALIAS> +<BUILD_ALIAS>Beta1</BUILD_ALIAS> It will also use the RELEASED version of our Kepler M6 target platform: -<TARGET_PLATFORM_VERSION>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION> +<TARGET_PLATFORM_VERSION>4.30.5.Alpha3</TARGET_PLATFORM_VERSION> -<TARGET_PLATFORM_VERSION_MAXIMUM>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION_MAXIMUM> +<TARGET_PLATFORM_VERSION_MAXIMUM>4.30.5.Alpha3</TARGET_PLATFORM_VERSION_MAXIMUM> *Your master branch's root pom.xml needs to use parent pom version 4.1.0.Beta1-SNAPSHOT* if you want to automatically adopt the Beta1 suffix in your jar qualifiers for your master branch builds, and to later pick up the forthcoming 4.30.5.Alpha4-SNAPSHOT target platform, which will be available in May when Kepler M7 is released [1]. [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule Note too that the parent pom in the stable branch (4.1.0.Alpha2x) has also been updated to use to use released 4.30.5.Alpha3 (Kepler M6) target platform. -<TARGET_PLATFORM_VERSION>4.30.5.Alpha3-SNAPSHOT</TARGET_PLATFORM_VERSION> +<TARGET_PLATFORM_VERSION>4.30.5.Alpha3</TARGET_PLATFORM_VERSION> -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com