[JBoss JIRA] (JBIDE-19236) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19236?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19236:
--------------------------------------
Assignee: Alexey Kazakov
> For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JavaEE]
> -----------------------------------------------------
>
> Key: JBIDE-19236
> URL: https://issues.jboss.org/browse/JBIDE-19236
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [JavaEE]: 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 JavaEE 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, 3 months
[JBoss JIRA] (JBIDE-19239) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [BrowserSim]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19239:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [BrowserSim]
Key: JBIDE-19239
URL: https://issues.jboss.org/browse/JBIDE-19239
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: browsersim
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [BrowserSim]: 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 BrowserSim 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, 3 months
[JBoss JIRA] (JBIDE-19240) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Webservices]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19240:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Webservices]
Key: JBIDE-19240
URL: https://issues.jboss.org/browse/JBIDE-19240
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: webservices
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Webservices]: 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 Webservices 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, 3 months
[JBoss JIRA] (JBIDE-19242) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19242:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Central]
Key: JBIDE-19242
URL: https://issues.jboss.org/browse/JBIDE-19242
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central, maven, project-examples
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Central]: 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 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, 3 months
[JBoss JIRA] (JBIDE-19243) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19243:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Portlet]
Key: JBIDE-19243
URL: https://issues.jboss.org/browse/JBIDE-19243
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: portal-gatein
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Portlet]: 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 Portlet 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, 3 months
[JBoss JIRA] (JBIDE-19241) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19241:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Arquillian]
Key: JBIDE-19241
URL: https://issues.jboss.org/browse/JBIDE-19241
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: testing-tools
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Arquillian]: 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 Arquillian 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, 3 months
[JBoss JIRA] (JBIDE-19244) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Freemarker]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19244:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [Freemarker]
Key: JBIDE-19244
URL: https://issues.jboss.org/browse/JBIDE-19244
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: freemarker
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [Freemarker]: 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 Freemarker 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, 3 months
[JBoss JIRA] (JBIDE-19245) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [LiveReload]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19245:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [LiveReload]
Key: JBIDE-19245
URL: https://issues.jboss.org/browse/JBIDE-19245
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [LiveReload]: 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 LiveReload 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, 3 months
[JBoss JIRA] (JBIDE-19235) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19235:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [OpenShift]
Key: JBIDE-19235
URL: https://issues.jboss.org/browse/JBIDE-19235
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [OpenShift]: 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 OpenShift 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, 3 months
[JBoss JIRA] (JBIDE-19236) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19236:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JavaEE]
Key: JBIDE-19236
URL: https://issues.jboss.org/browse/JBIDE-19236
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [JavaEE]: 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 JavaEE 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, 3 months