[jbosstools-dev] Still using the JBoss Tools 4.1.Alpha2 parent pom? Yes, and you SHOULD NOT BE! :: ACTION REQUIRED

[Nick Boldt]

<public-shaming-mode>

== Who is this email meant for? ==

These projects need to fix their root pom:

* Server (archives, as, jmx)
* Forge
* Openshift
* Webservices
* Hibernate

== What's wrong with my parent pom? ==

Reminder, if your root pom still points at the Alpha2 parent pom, You're 
Doing It Wrong, and need to fix this before code freeze next week. Your 
root pom needs to be bumped every time we branch, so it can build w/ the 
latest version from the master branch [0].

[0] 
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L7

This will also ensure you're using the correct target platform when you 
build locally. Since the Beta1 target platform is changing from Kepler 
M6 to M7 later this week, *THIS IS URGENT.*

== How do I know you haven't updated yet? ==

Other than looking at your sources in github, the easiest way to see 
who's conforming and who isn't is the JBT nightly aggregate site [1], 
which lists versions of features w/ their suffix. This suffix is 
inherited from the parent pom. So if you're using the Alpha2 parent pom, 
your features will have "Alpha2" in their qualifier.

[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/

== How do you fix your root pom? ==

Like this:

diff --git a/pom.xml b/pom.xml
index 4749cb1..28ef6ca 100644
--- a/pom.xml
+++ b/pom.xml
@@ -5,7 +5,7 @@
         <parent>
                 <groupId>org.jboss.tools</groupId>
                 <artifactId>parent</artifactId>
-               <version>4.1.0.Alpha2-SNAPSHOT</version>
+               <version>4.1.0.Beta1-SNAPSHOT</version>
 
<relativePath>../jbosstools-build/parent/pom.xml</relativePath>
         </parent>
         <groupId>org.jboss.tools</groupId>


</public-shaming-mode>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com