[JBoss JIRA] (JBIDE-16234) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16234:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]
Key: JBIDE-16234
URL: https://issues.jboss.org/browse/JBIDE-16234
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [OpenShift]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for OpenShift 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16235) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16235:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]
Key: JBIDE-16235
URL: https://issues.jboss.org/browse/JBIDE-16235
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [JavaEE]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for JavaEE 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16227) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16227:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Aerogear]
Key: JBIDE-16227
URL: https://issues.jboss.org/browse/JBIDE-16227
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [Aerogear]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for Aerogear 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16228) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16228:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]
Key: JBIDE-16228
URL: https://issues.jboss.org/browse/JBIDE-16228
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [JST]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16229) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16229:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [VPE]
Key: JBIDE-16229
URL: https://issues.jboss.org/browse/JBIDE-16229
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [VPE]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for VPE 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16230) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16230:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JBT Update Sites]
Key: JBIDE-16230
URL: https://issues.jboss.org/browse/JBIDE-16230
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [JBT Update Sites]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for JBT Update Sites 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16231) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16231:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
Key: JBIDE-16231
URL: https://issues.jboss.org/browse/JBIDE-16231
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Alpha1 [Server]: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...], or [Search for Server 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: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16226) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16226:
----------------------------------
Summary: For JBIDE 4.2.0.Alpha1: Code Freeze + Branch
Key: JBIDE-16226
URL: https://issues.jboss.org/browse/JBIDE-16226
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.2.0.Alpha1
For JBIDE 4.2.0.Alpha1: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...]
See also: JBDS-2855
--
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
12 years, 4 months
[JBoss JIRA] (JBDS-2855) For JBDS 8.0.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2855:
--------------------------------
Summary: For JBDS 8.0.0.Alpha1: Code Freeze + Branch
Key: JBDS-2855
URL: https://issues.jboss.org/browse/JBDS-2855
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 8.0.0.Alpha1
For JBDS 8.0.0.Alpha1: 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.Alpha1
[Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Alpha1x
git push origin jbosstools-4.2.0.Alpha1x
{code}
5. 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...]
--
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
12 years, 4 months