[jbosstools-issues] [JBoss JIRA] (JBIDE-22570) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-22570:
------------------------------------

A "downbump" is only a problem if we RELEASE something with 3.2.0, then decide we should have called it 3.1.1 and try to re-release it under the older number.

Since there's only been a CI build, we're fine. We'll just have to make sure to trash any Central nightly builds or else the larger version will be aggregated in favour of the newer timestamp but lower x.y.z version.

That said, there's also no harm in moving to x.(y+1) instead of x.y.(z+1). Just don't do that for the foundation plugin that defines the "version" of JBoss Tools. :D

> For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Central]
> ----------------------------------------------------------
>
>                 Key: JBIDE-22570
>                 URL: https://issues.jboss.org/browse/JBIDE-22570
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: central, maven, project-examples
>    Affects Versions: 4.4.1.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Fred Bricon
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.4.1.Alpha1
>
>
> For JBIDE 4.4.1.Alpha1 [Central]: Please perform the following tasks:
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*:
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.4.1.Alpha1-SNAPSHOT</version>
>   </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. 
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0)
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.1.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.1.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.1.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.1.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22maven%22%2C%22central%22%2C%22project-examples%22%29]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)