[jbosstools-issues] [JBoss JIRA] (JBIDE-17330) For JBIDE 4.2.0.Beta2: Code Freeze + Branch [Base]

Thu May 22 20:14:57 EDT 2014

     [ https://issues.jboss.org/browse/JBIDE-17330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-17330:
-------------------------------------

    Comment: was deleted

(was: build works fine here:

{code}
[INFO] openshift.all ..................................... SUCCESS [10.875s]
[INFO] openshift.plugins ................................. SUCCESS [0.007s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [1.900s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.356s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.840s]
[INFO] org.jboss.tools.openshift.express.core ............ SUCCESS [1.331s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [4.288s]
[INFO] openshift.tests ................................... SUCCESS [0.008s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [26.579s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [39.274s]
[INFO] openshift.features ................................ SUCCESS [0.010s]
[INFO] org.jboss.tools.openshift.egit.integration.feature  SUCCESS [0.142s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.198s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature  SUCCESS [0.106s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.138s]
[INFO] openshift.site .................................... SUCCESS [25.174s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:06.196s
[INFO] Finished at: Fri May 23 02:01:08 CEST 2014
[INFO] Final Memory: 88M/940M
[INFO] ------------------------------------------------------------------------
{code})


> For JBIDE 4.2.0.Beta2: Code Freeze + Branch [Base]
> --------------------------------------------------
>
>                 Key: JBIDE-17330
>                 URL: https://issues.jboss.org/browse/JBIDE-17330
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: common/jst/core, usage
>            Reporter: Nick Boldt
>            Assignee: Alexey Kazakov
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.2.0.Beta2
>
>
> For JBIDE 4.2.0.Beta2 [Base]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta2
> [Unresolved JIRAs with fixVersion = 4.2.0.Beta2, 8.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.2.0.Beta2%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%228.0.0.Beta2%22%29%29%29%20and%20resolution%20%3D%20Unresolved]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. 
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Beta2-SNAPSHOT; 
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.2.0.Beta2-SNAPSHOT</version>
>   </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Beta3  # (if the TP is already released)
>   or 
> mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta2x{color}* branch; 
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Beta2x
> git push origin jbosstools-4.2.0.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta2-SNAPSHOT{color}*:
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.2.0.Beta2-SNAPSHOT</version>
>   </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta2x{color}* branch, and
> * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%29%20and%20fixVersion%20%3D%20%228.0.0.Beta2%22%29%20or%20%28project%20in%20%28JBIDE%29%20and%20fixVersion%20%3D%20%224.2.0.Beta2%22%29%29%20AND%20%28labels%20%3D%20new_and_noteworthy%20OR%20summary%20~%20%22New%20and%20Noteworthy%20for%204.2.0.Beta2%22%29%20AND%20resolution%20is%20null] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%228.0.0.Beta2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.Beta2%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%228.0.0.Beta2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.Beta2%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29]


--
This message was sent by Atlassian JIRA
(v6.2.3#6260)