April 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26620) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [central-update]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26620?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26620: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [central-update] > --------------------------------------------------------------------------- > > Key: JBIDE-26620 > URL: https://issues.jboss.org/browse/JBIDE-26620 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26619) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [updatesite]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26619: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [updatesite] Key: JBIDE-26619 URL: https://issues.jboss.org/browse/JBIDE-26619 Project: Tools (JBoss Tools) Issue Type: Task Components: updatesite Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [updatesite]: 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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26619) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [updatesite]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26619?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26619: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [updatesite] > ----------------------------------------------------------------------- > > Key: JBIDE-26619 > URL: https://issues.jboss.org/browse/JBIDE-26619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [updatesite]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26618) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [integration-tests]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26618?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26618: ---------------------------------- Assignee: Pavol Srna > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [integration-tests] > ------------------------------------------------------------------------------ > > Key: JBIDE-26618 > URL: https://issues.jboss.org/browse/JBIDE-26618 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Jeff MAURY > Assignee: Pavol Srna > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [integration-tests]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [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 (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26618) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [integration-tests]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26618: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [integration-tests] Key: JBIDE-26618 URL: https://issues.jboss.org/browse/JBIDE-26618 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [integration-tests]: 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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [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 (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26617) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [webservices]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26617?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26617: ---------------------------------- Assignee: Jeff MAURY > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [webservices] > ------------------------------------------------------------------------ > > Key: JBIDE-26617 > URL: https://issues.jboss.org/browse/JBIDE-26617 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [webservices]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [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 (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26617) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [webservices]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26617: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [webservices] Key: JBIDE-26617 URL: https://issues.jboss.org/browse/JBIDE-26617 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [webservices]: 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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [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 (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26605) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26605?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-26605. ------------------------------ Resolution: Done > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26605 > URL: https://issues.jboss.org/browse/JBIDE-26605 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [foundation]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26616) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [visual-page-editor-core]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26616?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26616: ---------------------------------- Assignee: Ilya Buziuk > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [visual-page-editor-core] > ------------------------------------------------------------------------------------ > > Key: JBIDE-26616 > URL: https://issues.jboss.org/browse/JBIDE-26616 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [visual-page-editor-core]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26605) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation]

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26605?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26605: ------------------------------------ bump up to parent pom version = 4.12.0.AM1-SNAPSHOT > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26605 > URL: https://issues.jboss.org/browse/JBIDE-26605 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [foundation]: 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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-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.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2019