]
Alexey Kazakov closed JBIDE-15948.
----------------------------------
For JBIDE 4.1.1.CR1: Code Freeze + Branch [JST]
-----------------------------------------------
Key: JBIDE-15948
URL:
https://issues.jboss.org/browse/JBIDE-15948
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Labels: task
Fix For: 4.1.1.CR1
For JBIDE 4.1.1.CR1 [JST]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion =
4.1.1.CR1
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.1.1.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.CR1-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.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
{code}
or{code}
mvn clean verify -Dtpc.version=4.31.0.Final
mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not
CR1x) branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.x
git push origin jbosstools-4.1.1.x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...],
or [Search for JST task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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: