[JBoss JIRA] (JBIDE-19237) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19237:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Birt]
Key: JBIDE-19237
URL: https://issues.jboss.org/browse/JBIDE-19237
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: birt
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Birt]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19238) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Forge]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19238:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Forge]
Key: JBIDE-19238
URL: https://issues.jboss.org/browse/JBIDE-19238
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Forge]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19230) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19230:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JBT Update Sites]
Key: JBIDE-19230
URL: https://issues.jboss.org/browse/JBIDE-19230
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [JBT Update Sites]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19232) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19232:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Server]
Key: JBIDE-19232
URL: https://issues.jboss.org/browse/JBIDE-19232
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19231) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19231:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Central Discovery]
Key: JBIDE-19231
URL: https://issues.jboss.org/browse/JBIDE-19231
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Central Discovery]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19233) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19233:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Hibernate]
Key: JBIDE-19233
URL: https://issues.jboss.org/browse/JBIDE-19233
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19234) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19234:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Base]
Key: JBIDE-19234
URL: https://issues.jboss.org/browse/JBIDE-19234
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core, usage
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Base]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3346) For JBDS 9.0.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3346:
--------------------------------
Summary: For JBDS 9.0.0.Alpha1: Code Freeze + Branch
Key: JBDS-3346
URL: https://issues.jboss.org/browse/JBDS-3346
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 9.0.0.Alpha1
For JBDS 9.0.0.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19226) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19226:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch
Key: JBIDE-19226
URL: https://issues.jboss.org/browse/JBIDE-19226
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.3.0.Alpha1
For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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-3346
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19227) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19227:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Aerogear]
Key: JBIDE-19227
URL: https://issues.jboss.org/browse/JBIDE-19227
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Aerogear]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.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 was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months