August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24439) Block PRs for merge untill the Jenkins build is successful (protected branches)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24439?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24439: ------------------------------- Summary: Block PRs for merge untill the Jenkins build is successful (protected branches) (was: Block PRs for merge untill the Jenkins build is successful) > Block PRs for merge untill the Jenkins build is successful (protected branches) > ------------------------------------------------------------------------------- > > Key: JBIDE-24439 > URL: https://issues.jboss.org/browse/JBIDE-24439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: LATER > > > As discussed in this thread [1], we'd like to implement *Protected Branches* and > *Required Status Checks* [2] for some jbosstools-* projects. > [1] http://lists.jboss.org/pipermail/jbosstools-dev/2017-May/011948.html > [2] https://help.github.com/articles/defining-the-mergeability-of-pull-requests/ > We will therefore need to document some requirements in jbosstools-devdoc about how to properly submit PRs when version-bumping is required: > {quote}Make sure if your PR requires a version bump that the PR includes TWO commits. One for the change, and one for the version bump. That way the pair of commits can be built in the PR build and verify it works, AND when cherry picking the commit across branches, you can pick only the change and not the version-bump commit too. > {quote} > And we need to decide if we want to do what Fuse Tools does and require that PRs be reviewed before they can be merged, if we're ready to have that additional overhead on every PR. > [~jeffmaury] as project lead can you state which project(s) you'd like to see changed in github, and which ones should be changed as such: > * jbosstools-_____ > ** Protected Branch = master > ** Required Status Check(s) = ....? (which checks do we want) > ** PR reviews required = [true/false] > From that list of projects / requirements, we can then create subtask JIRAs to track the workj & the changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24866. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24866: ---------------------------------- Summary: For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] Key: JBIDE-24866 URL: https://issues.jboss.org/browse/JBIDE-24866 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools-extras Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.1.AM1 For JBIDE 4.5.1.AM1 [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.5.1.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.1.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.1.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.70.2.Final {code} mvn clean verify -Dtpc.version=4.70.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final {code} mvn clean verify -Dtpc.version=4.70.2.Final {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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24866: ---------------------------------- Assignee: Lars Heinemann > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24866: ------------------------------------ bump up to parent pom version = 4.5.1.AM1-SNAPSHOT > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24865) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24865?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24865. ------------------------------ Resolution: Done > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-24865 > URL: https://issues.jboss.org/browse/JBIDE-24865 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4507) For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer]

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4507: -------------------------------- Summary: For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer] Key: JBDS-4507 URL: https://issues.jboss.org/browse/JBDS-4507 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 11.1.0.AM1 For JBDS 11.1.0.AM1 [installer]: 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.5.1.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.1.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.1.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.70.2.Final {code} mvn clean verify -Dtpc.version=4.70.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final {code} mvn clean verify -Dtpc.version=4.70.2.Final {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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4507) For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4507?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4507: -------------------------------- Assignee: Jeff MAURY > For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4507 > URL: https://issues.jboss.org/browse/JBDS-4507 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.1.0.AM1 > > > For JBDS 11.1.0.AM1 [installer]: 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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4507) For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4507?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4507: ---------------------------------- bump up to parent pom version = 4.5.1.AM1-SNAPSHOT > For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4507 > URL: https://issues.jboss.org/browse/JBDS-4507 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.1.0.AM1 > > > For JBDS 11.1.0.AM1 [installer]: 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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4507) For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4507?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4507. ---------------------------- Resolution: Done > For JBDS 11.1.0.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4507 > URL: https://issues.jboss.org/browse/JBDS-4507 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.1.0.AM1 > > > For JBDS 11.1.0.AM1 [installer]: 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.5.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.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.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2017