June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27340) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [quarkus]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27340?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27340. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [quarkus] > ----------------------------------------------------------------------- > > Key: JBIDE-27340 > URL: https://issues.redhat.com/browse/JBIDE-27340 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: quarkus > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [quarkus]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for quarkus task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27337) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [openshift]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27337?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27337. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [openshift] > ------------------------------------------------------------------------- > > Key: JBIDE-27337 > URL: https://issues.redhat.com/browse/JBIDE-27337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Stephane Bouchet > Assignee: André Dietisheim > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [openshift]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for openshift task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27338) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [server]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27338?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27338: ------------------------------------------ bump up to parent pom version = 4.16.0.Final-SNAPSHOT > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [server] > ---------------------------------------------------------------------- > > Key: JBIDE-27338 > URL: https://issues.redhat.com/browse/JBIDE-27338 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Stephane Bouchet > Assignee: Robert Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [server]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for server task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27338) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [server]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27338?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27338. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [server] > ---------------------------------------------------------------------- > > Key: JBIDE-27338 > URL: https://issues.redhat.com/browse/JBIDE-27338 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Stephane Bouchet > Assignee: Robert Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [server]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for server task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27344) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [central-update]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27344?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27344. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [central-update] > ------------------------------------------------------------------------------ > > Key: JBIDE-27344 > URL: https://issues.redhat.com/browse/JBIDE-27344 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [central-update]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for central-update task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27330) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27330?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27330: ------------------------------------------ bump up to parent pom version = 4.16.0.Final-SNAPSHOT > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge] > --------------------------------------------------------------------- > > Key: JBIDE-27330 > URL: https://issues.redhat.com/browse/JBIDE-27330 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Stephane Bouchet > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [forge]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for forge task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27330) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27330?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27330. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [forge] > --------------------------------------------------------------------- > > Key: JBIDE-27330 > URL: https://issues.redhat.com/browse/JBIDE-27330 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Stephane Bouchet > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [forge]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for forge task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27331) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27331?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27331: ------------------------------------------ bump up to parent pom version = 4.16.0.Final-SNAPSHOT > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools] > ------------------------------------------------------------------------- > > Key: JBIDE-27331 > URL: https://issues.redhat.com/browse/JBIDE-27331 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Stephane Bouchet > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [fusetools]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27331) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27331?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27331. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools] > ------------------------------------------------------------------------- > > Key: JBIDE-27331 > URL: https://issues.redhat.com/browse/JBIDE-27331 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Stephane Bouchet > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [fusetools]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27332) For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools-extras]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27332?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27332: ------------------------------------------ bump up to parent pom version = 4.16.0.Final-SNAPSHOT > For JBIDE 4.16.0.Final: Prepare for 4.16.0.Final / 12.16.0.GA [fusetools-extras] > -------------------------------------------------------------------------------- > > Key: JBIDE-27332 > URL: https://issues.redhat.com/browse/JBIDE-27332 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Stephane Bouchet > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.16.0.Final > > > For JBIDE 4.16.0.Final [fusetools-extras]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.16.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.16.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.16.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.redhat.com/issues/?jql=%28%28project%20%3D%20%22JBID...] to do, please complete them next. > > [Search for all task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for fusetools-extras task JIRA|https://issues.redhat.com/issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2020