<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Here is a JIRA for that
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://issues.jboss.org/browse/JBIDE-14091">https://issues.jboss.org/browse/JBIDE-14091</a><br>
<br>
On 04/18/2013 01:53 PM, Nick Boldt wrote:<br>
</div>
<blockquote cite="mid:51705D3C.30406@redhat.com" type="cite">
<pre wrap="">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]
<a class="moz-txt-link-freetext" href="https://github.com/jbosstools/jbosstools-jst/commit/d50e176f93c6c585a93194c38fb42cd478a543db">https://github.com/jbosstools/jbosstools-jst/commit/d50e176f93c6c585a93194c38fb42cd478a543db</a>
I hope to see the nightly trunk site [1] only contain Beta1 bits soon.
It currently has a lot of Alpha2 in it.
[1] <a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/updates/nightly/core/trunk/">http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</a>
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 <a class="moz-txt-link-rfc2396E" href="mailto:nboldt@redhat.com"><nboldt@redhat.com></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:jbosstools-dev@lists.jboss.org"><jbosstools-dev@lists.jboss.org></a>
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] <a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule">http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule</a>
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>
</pre>
</blockquote>
<br>
</body>
</html>