[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20951:
------------------------------------
Root pom updated to the correct parent pom reference...
https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstool...
... but your plugins are still at version 4.3.0, not 4.3.1. Did you ever do a 4.3.0 release, or are you STILL working toward your 4.3.0.Final bits?
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
> -------------------------------------------------------------------
>
> Key: JBIDE-20951
> URL: https://issues.jboss.org/browse/JBIDE-20951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20963?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20963:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices]
> -------------------------------------------------------------
>
> Key: JBIDE-20963
> URL: https://issues.jboss.org/browse/JBIDE-20963
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Webservices]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20948:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear]
> ----------------------------------------------------------
>
> Key: JBIDE-20948
> URL: https://issues.jboss.org/browse/JBIDE-20948
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Aerogear]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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 was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20953?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20953:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server]
> --------------------------------------------------------
>
> Key: JBIDE-20953
> URL: https://issues.jboss.org/browse/JBIDE-20953
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Server]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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 was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20951:
----------------------------------
Assignee: Martin Malina
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
> -------------------------------------------------------------------
>
> Key: JBIDE-20951
> URL: https://issues.jboss.org/browse/JBIDE-20951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20957:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
> ------------------------------------------------------------
>
> Key: JBIDE-20957
> URL: https://issues.jboss.org/browse/JBIDE-20957
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20967?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20967:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload]
> ------------------------------------------------------------
>
> Key: JBIDE-20967
> URL: https://issues.jboss.org/browse/JBIDE-20967
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [LiveReload]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20947:
------------------------------------
As of 2015-10-20 found these root pom versions INCORRECT:
{code}
aerogear :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
livereload :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
playground :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
server :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
webservices :: <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.3.0.Final-SNAPSHOT</version> </parent>
{code}
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1
> -----------------------------------------------
>
> Key: JBIDE-20947
> URL: https://issues.jboss.org/browse/JBIDE-20947
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-523:
-------------------------------------------
btw. afaics default JBDS 9 JBoss perspective out of the box today have Fuse Integration in the the Perspective list, no need to use "Other...." and Fuse Integration is listed front and center on first start in Central.
So not sure setting the default perspective changes much ?
> Create a demonstration/ prototype installer for Fuse Tooling support
> --------------------------------------------------------------------
>
> Key: JBTIS-523
> URL: https://issues.jboss.org/browse/JBTIS-523
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Optional
> Attachments: sai1.png
>
>
> The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
> Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
> Here's a usability scenario targeting Fuse Tooling:
> {code}
> Test scenario A:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
> 4. Select the Software/Update tab in the JBoss Central view.
> 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
> 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
> Select the following item:
> JBoss Fuse Development
> 7. Accept/ respond 'Yes' and restart
> 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario B:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario C:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario D: (future - not available currently)
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> JBDS comes up in the Fuse Integration perspective - read to go.
> {code}
> Comments welcome!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-523:
-------------------------------------------
Are we only talking about the install experience via the installer or overall install of Fuse ?
The installer is by far the least used afaics so if we only look at this from installer perspective we will not cover the paths of BYOE (bring your own eclipse) for users using eclipse market place.
If just caring about installation could be solved by adding a Fuse specific marketplace entry that just contains the Fuse functionallity as done for the IS marketplace entry. This would still install the required JBDS core parts, incl. central.
Is this just about having a way to install it easily or also about how Fuse will be configured in eclipse ? Then setting first perspectives are bad/not enough IMO. Maybe Fuse could add entries to JBoss perspective ? and beyond that is making Fuse quickstarts etc. available from JBoss Central so anyone can get to Fuse even without having first installed Fuse and once installed have access to all the Fuse quickstarts.
> Create a demonstration/ prototype installer for Fuse Tooling support
> --------------------------------------------------------------------
>
> Key: JBTIS-523
> URL: https://issues.jboss.org/browse/JBTIS-523
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Optional
> Attachments: sai1.png
>
>
> The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
> Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
> Here's a usability scenario targeting Fuse Tooling:
> {code}
> Test scenario A:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
> 4. Select the Software/Update tab in the JBoss Central view.
> 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
> 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
> Select the following item:
> JBoss Fuse Development
> 7. Accept/ respond 'Yes' and restart
> 8. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario B:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario C:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario D: (future - not available currently)
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> JBDS comes up in the Fuse Integration perspective - read to go.
> {code}
> Comments welcome!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months