[jbosstools-issues] [JBoss JIRA] (JBIDE-16195) For JBIDE 4.1.1.Final: Prepare for Final/GA release

Nick Boldt (JIRA) issues at jboss.org
Mon Dec 16 10:16:35 EST 2013


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

Nick Boldt commented on JBIDE-16195:
------------------------------------

[~maxandersen] [~fbricon]: 

Two questions about the JBDS 7.1 announcement blog [1]  ...

a) shouldn't we link to Kepler SR1, instead of Kepler R?

b) should the topic in this channel be updated to point to the JBDS 7.1 blog instead of the 7.0 one?

[1] https://community.jboss.org/en/tools/blog/2013/12/16/jboss-tool-411-and-jbds-71-released
                
> For JBIDE 4.1.1.Final: Prepare for Final/GA release
> ---------------------------------------------------
>
>                 Key: JBIDE-16195
>                 URL: https://issues.jboss.org/browse/JBIDE-16195
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: build
>            Reporter: Nick Boldt
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.1.1.CR1%22%2C%20%224.1.1.Final%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%227.1.0.CR1%22%2C%227.1.0.GA%22%29%29%29%20and%20resolution%20%3D%20Unresolved]
> 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}*
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.1.1.Final-SNAPSHOT</version>
>   </parent>
> {code}
> 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}*
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.1.2.Alpha1-SNAPSHOT</version>
>   </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.30.6.Final
> mvn clean verify -Dtpc.version=4.31.1.Final
> {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+%227.1.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Final%22%29%29+AND+labels+%3D+task]
> See also: JBDS-2846

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list