[jbosstools-issues] [JBoss JIRA] (JBIDE-19017) Prepare for 4.2.2.Final release

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031127#comment-13031127 ] 

Nick Boldt commented on JBIDE-19017:
------------------------------------

Central, Forge, WS are now rebuilding:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-central_4.2.luna/115/console

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-forge_4.2.luna/84/console

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-webservices_4.2.luna/81/console

> Prepare for 4.2.2.Final release
> -------------------------------
>
>                 Key: JBIDE-19017
>                 URL: https://issues.jboss.org/browse/JBIDE-19017
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.2.2.Final
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>            Priority: Blocker
>             Fix For: 4.2.2.Final
>
>
> TODOs for preparing for the 4.2.2 release.
> For components that contribute to this release (and only these): Central, WS, Forge, JBT aggregates, JBDS:
> a) ensure we're all using the right TP (4.40.0.Final, 4.41.1.Final) & parent pom version 4.2.1.Final-SNAPSHOT - NO CHANGE SINCE 4.2.1 release; all projects OK
> b) ensure components have properly upversioned to 4.2.2/8.0.2, etc.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)