[JBoss JIRA] (JBIDE-15527) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15527?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-15527.
------------------------------
Assignee: Nick Boldt
Resolution: Done
All subtasks done.
According to JIRA status, only these 10 builds need to be run:
Base
Forge
Server
Livereload
Openshift
Webservices
VPE
JST
JavaEE
Central
then ...
JBT + JBDS aggregates
> 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
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> 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}
> *{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
> 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, 6 months
[JBoss JIRA] (JBIDE-15544) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15544?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-15544.
-------------------------------
Resolution: Done
Branch pushed to GH
> 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
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15544) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central]
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15544?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-15544:
-----------------------------------
Assignee: Fred Bricon
> 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
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-15435) "installed plugins" detection seems fishy in project examples / central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15435?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15435:
--------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.1.Alpha2)
> "installed plugins" detection seems fishy in project examples / central
> -----------------------------------------------------------------------
>
> Key: JBIDE-15435
> URL: https://issues.jboss.org/browse/JBIDE-15435
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.1.Beta1
>
>
> Following JBDS-2753, [~maxandersen] says he installed the JBoss GWT connector, which dragged the GPE plugins.
> Some functionality seem missing according to Max (which ones?). In the JBoss Central 'software updates' page, the GWT/GPE connector is shown as missing. In the GWT example wizard, the feature appears as installed. One of the 2 is wrong, obviously.
--
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-15533) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15533?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-15533.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> 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
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> 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, 6 months