[JBoss JIRA] (JBIDE-21498) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21498:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Hibernate]
Key: JBIDE-21498
URL: https://issues.jboss.org/browse/JBIDE-21498
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21499) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21499:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Base]
Key: JBIDE-21499
URL: https://issues.jboss.org/browse/JBIDE-21499
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: usage, common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Base]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21500) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21500:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [OpenShift]
Key: JBIDE-21500
URL: https://issues.jboss.org/browse/JBIDE-21500
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [OpenShift]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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 was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21501) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Playground]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21501:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Playground]
Key: JBIDE-21501
URL: https://issues.jboss.org/browse/JBIDE-21501
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: playground
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Playground]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21503) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21503:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JST]
Key: JBIDE-21503
URL: https://issues.jboss.org/browse/JBIDE-21503
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [JST]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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 was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21502) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21502:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JavaEE]
Key: JBIDE-21502
URL: https://issues.jboss.org/browse/JBIDE-21502
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: seam2, cdi, cdi-extensions, jsf
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [JavaEE]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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 was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21505) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Birt]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21505:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Birt]
Key: JBIDE-21505
URL: https://issues.jboss.org/browse/JBIDE-21505
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: birt
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Birt]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21504) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21504:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Forge]
Key: JBIDE-21504
URL: https://issues.jboss.org/browse/JBIDE-21504
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Forge]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21495) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21495:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
Key: JBIDE-21495
URL: https://issues.jboss.org/browse/JBIDE-21495
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: qa
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Integration Tests]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21496) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21496:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
Key: JBIDE-21496
URL: https://issues.jboss.org/browse/JBIDE-21496
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months