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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-19017:
----------------------------------------

http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-sites.aggregate.site_4.2.luna/all/repo/ contains Central 1.3.2.Final-v20150108-2329-B115, webservices 1.7.2.Final-v20150108-2329-B81 and forge 1.3.2.Final-v20150108-2321-B84. So content seems to be fine.
However, it's index file is still telling it's a 4.2.1 version. I'll suggest a PR that fixes that in the jbosstools-build-sites repo.

> 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)