[JBoss JIRA] (JBIDE-15527) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15527:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
Key: JBIDE-15527
URL: https://issues.jboss.org/browse/JBIDE-15527
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.1.1.Alpha2
For JBIDE 4.1.1.Alpha2: 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...]
See also: JBDS-2773
--
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, 7 months
[JBoss JIRA] (JBIDE-15528) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15528:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Aerogear]
Key: JBIDE-15528
URL: https://issues.jboss.org/browse/JBIDE-15528
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Aerogear]: 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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15529) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15529:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JST]
Key: JBIDE-15529
URL: https://issues.jboss.org/browse/JBIDE-15529
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [JST]: 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 JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15530) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15530:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
Key: JBIDE-15530
URL: https://issues.jboss.org/browse/JBIDE-15530
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [VPE]: 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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15531) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [XULRunner]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15531:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [XULRunner]
Key: JBIDE-15531
URL: https://issues.jboss.org/browse/JBIDE-15531
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: xulrunner
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [XULRunner]: 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 XULRunner 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, 7 months
[JBoss JIRA] (JBIDE-15532) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15532:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [JBT Update Sites]
Key: JBIDE-15532
URL: https://issues.jboss.org/browse/JBIDE-15532
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [JBT Update Sites]: 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 JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15533) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-15533:
----------------------------------
Summary: For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central Discovery]
Key: JBIDE-15533
URL: https://issues.jboss.org/browse/JBIDE-15533
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Alpha2 [Central Discovery]: 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 Discovery 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, 7 months
[JBoss JIRA] (JBDS-2773) For JBDS 7.1.0.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2773:
--------------------------------
Summary: For JBDS 7.1.0.Alpha2: Code Freeze + Branch
Key: JBDS-2773
URL: https://issues.jboss.org/browse/JBDS-2773
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 7.1.0.Alpha2
For JBDS 7.1.0.Alpha2: 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...]
--
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, 7 months
[JBoss JIRA] (JBIDE-15526) JAX-RS validation problems are not linked
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15526?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15526:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.1.1.Alpha2)
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-15526
> URL: https://issues.jboss.org/browse/JBIDE-15526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Jaroslav Jankovič
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 7 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-12860:
----------------------------------
Fix Version/s: 4.1.1.Alpha2
(was: 4.2.x)
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Alpha2
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 7 months