[JBoss JIRA] (JBIDE-15541) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15541:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge]
Key: JBIDE-15541
URL: https://issues.jboss.org/browse/JBIDE-15541
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Forge]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge 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, 9 months
[JBoss JIRA] (JBIDE-15544) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15544:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central]
Key: JBIDE-15544
URL: https://issues.jboss.org/browse/JBIDE-15544
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central, maven, project-examples
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Central]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central 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, 9 months
[JBoss JIRA] (JBIDE-15546) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Freemarker]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15546:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Freemarker]
Key: JBIDE-15546
URL: https://issues.jboss.org/browse/JBIDE-15546
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: freemarker
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Freemarker]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker 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, 9 months
[JBoss JIRA] (JBIDE-15545) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Portlet]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15545:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Portlet]
Key: JBIDE-15545
URL: https://issues.jboss.org/browse/JBIDE-15545
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: portal-gatein
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Portlet]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet 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, 9 months
[JBoss JIRA] (JBIDE-15547) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [LiveReload]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15547:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [LiveReload]
Key: JBIDE-15547
URL: https://issues.jboss.org/browse/JBIDE-15547
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: livereload
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [LiveReload]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload 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, 9 months
[JBoss JIRA] (JBIDE-15534) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15534:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Server]
Key: JBIDE-15534
URL: https://issues.jboss.org/browse/JBIDE-15534
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for 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, 9 months
[JBoss JIRA] (JBIDE-15536) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15536:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Base]
Key: JBIDE-15536
URL: https://issues.jboss.org/browse/JBIDE-15536
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: usage
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Base]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base 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, 9 months
[JBoss JIRA] (JBIDE-15537) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15537:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [OpenShift]
Key: JBIDE-15537
URL: https://issues.jboss.org/browse/JBIDE-15537
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [OpenShift]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for 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, 9 months
[JBoss JIRA] (JBIDE-15538) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15538:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JavaEE]
Key: JBIDE-15538
URL: https://issues.jboss.org/browse/JBIDE-15538
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [JavaEE]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for 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, 9 months
[JBoss JIRA] (JBIDE-15535) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15535:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Hibernate]
Key: JBIDE-15535
URL: https://issues.jboss.org/browse/JBIDE-15535
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate 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, 9 months