[jbosstools-dev] Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released

[Nick Boldt]

There were actually 10 JIRAs associated with this new target platform, 
not 6.

Here's an updated query, which includes the missing JIRAs for JBIDE 
*and* JBDS:

https://issues.jboss.org/issues/?jql=component%3Dtarget-platform%20and%20%28%28project%3DJBIDE%20and%20fixVersion%3D4.2.0.Beta3%29%20or%20%28project%3DJBDS%20and%20fixVersion%3D8.0.0.Beta3%29%29

I've also created a new "target-platform" component in JBDS to match the 
one in JBIDE.

On 07/08/2014 09:14 AM, Mickael Istria wrote:
> Target Platform 4.40.0.Beta4 for JBoss Tools 4.2.0.Beta3 has been released
>
> Changes
> =======
>
> Here is the list of changes since 4.40.0.Beta3 release:https://issues.jboss.org/issues/?jql=project%3DJBIDE%20and%20component%3Dtarget-platform%20and%20fixVersion%3D4.2.0.Beta3
>
> Usage
> =====
>
> Target platform 4.40.0.Beta4 is what JBoss Tools 4.2.0.Beta3 should have used, and what it will use for next builds and respins.
>
> All Jenkins jobs for branch jbosstools-4.2.0.Beta3x and parent pom 4.2.0.Beta3-SNAPSHOT have been updated to use target platform 4.40.0.Beta4.
>
> The following p2 repositories *will be modified* to point to this new target platform once JBoss Tools 4.2.0.Beta3 is released:
> *http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/
> *http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/luna/
>
> Until then, you can access the target platform at the URLs below.
>
> Download
> ========
>
> Update site:http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.40.0.Beta4/REPO/
> Update site zip:http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstarget/4.40.0.Beta4/jbosstoolstarget-4.40.0.Beta4.zip
> Git tag:https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.0.Beta4
>
> Testing/Development
> ===================
>
> If your root pom correctly specifies the latest parent pom version as 4.2.0.Beta3-SNAPSHOT, you need only this:
>    $ mvn clean verify
>
> If you're using a different parent pom, use this:
>    $ mvn clean verify -Dtpc.version=${TARGET_PLATFORM_VERSION}
>
> For usage and help (using in IDE, building a mirror locally, using a zip), see:https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_for_consumers.md
>
> What's next?
> ============
>
> jbosstools-target-platforms project branch 4.40.x has been prepared for potential upgrades, and its version is now 4.40.0.CR1-SNAPSHOT.  We can at least expect for this version:
> * Adoption of Eclipse THyM
> * Update or Tern plugins
> * Shall you need anything else, please follow those instructions to request a change ASAP:https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc
>
> Deadline for changes in target platform 4.40.0.Beta4-SNAPSHOT is**Monday, August 25th**
>
> All Jenkins jobs for *master* and parent pom 4.2.0.CR1-SNAPSHOT have been updated to use target platform 4.40.0.CR1-SNAPSHOT
>
> --
> 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 at 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