[JBoss JIRA] (JBIDE-15523) Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15523?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15523:
-------------------------------------
Attachment: embedded-cartridges-lables-fixed.png
> Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15523
> URL: https://issues.jboss.org/browse/JBIDE-15523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: embeddable-carts-with-descriptions.png, embedded-cartridges-lables-fixed.png
>
>
> With the update to the latest OpenShift client (?) the OpenShift application / import wizard displays the embeddable (add-on) cartridges with their (very verbose) description where they should get shown with their display name:
> !embeddable-carts-with-descriptions.png!
> In consequence it's very awkward for some cartridges to know what cartridge is listed (not all embeddable cartridges start with their name in the description).
> Standalone (Web-) cartridges are not affected.
--
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, 6 months
[JBoss JIRA] (JBIDE-15523) Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15523?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-15523:
----------------------------------------
Assignee: Andre Dietisheim
> Application wizard: Embeddable (Add-on) cartridges are displayed with their description and not with their display names
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15523
> URL: https://issues.jboss.org/browse/JBIDE-15523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: embeddable-carts-with-descriptions.png, embedded-cartridges-lables-fixed.png
>
>
> With the update to the latest OpenShift client (?) the OpenShift application / import wizard displays the embeddable (add-on) cartridges with their (very verbose) description where they should get shown with their display name:
> !embeddable-carts-with-descriptions.png!
> In consequence it's very awkward for some cartridges to know what cartridge is listed (not all embeddable cartridges start with their name in the description).
> Standalone (Web-) cartridges are not affected.
--
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, 6 months
[JBoss JIRA] (JBIDE-15539) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15539?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-15539.
-----------------------------------
Resolution: Rejected
There are no changes.
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-15539
> URL: https://issues.jboss.org/browse/JBIDE-15539
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Birt]: 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 Birt 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, 6 months
[JBoss JIRA] (JBIDE-15543) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15543?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-15543.
-----------------------------------
Resolution: Rejected
There are no changes.
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Arquillian]
> ---------------------------------------------------------
>
> Key: JBIDE-15543
> URL: https://issues.jboss.org/browse/JBIDE-15543
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Arquillian]: 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 Arquillian 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, 6 months
[JBoss JIRA] (JBIDE-15545) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Portlet]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15545?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-15545.
-----------------------------------
Resolution: Rejected
There are no changes.
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15539) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15539?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-15539:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-15539
> URL: https://issues.jboss.org/browse/JBIDE-15539
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Birt]: 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 Birt 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, 6 months
[JBoss JIRA] (JBIDE-15545) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Portlet]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15545?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-15545:
-------------------------------------
Assignee: Snjezana Peco
> 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
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15543) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15543?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-15543:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Arquillian]
> ---------------------------------------------------------
>
> Key: JBIDE-15543
> URL: https://issues.jboss.org/browse/JBIDE-15543
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [Arquillian]: 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 Arquillian 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, 6 months
[JBoss JIRA] (JBIDE-15541) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15541?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-15541.
-------------------------------
Resolution: Rejected
> 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
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15535) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15535?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-15535:
---------------------------------
Assignee: Koen Aers
> 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
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months