July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3871: -------------------------------- Fix Version/s: 12.9.0.AM1 (was: 12.x) > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 12.9.0.AM1 > > Attachments: screenshot-1.png > > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26196) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [integration-tests]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26197) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [updatesite]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26197) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [updatesite]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26197) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [updatesite]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26197) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [updatesite]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26198) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update]

by Nick Boldt (JIRA)

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

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26198) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26198: ---------------------------------- Summary: For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update] Key: JBIDE-26198 URL: https://issues.jboss.org/browse/JBIDE-26198 Project: Tools (JBoss Tools) Issue Type: Task Components: central-update Reporter: Nick Boldt Priority: Blocker Fix For: 4.9.0.AM1 For JBIDE 4.9.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.9.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.9.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.9.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.80.1.Final {code} mvn clean verify -Dtpc.version=4.80.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.1.Final {code} mvn clean verify -Dtpc.version=4.80.1.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.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26198) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26198?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26198: ------------------------------------ bump up to parent pom version = 4.9.0.AM1-SNAPSHOT > For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-26198 > URL: https://issues.jboss.org/browse/JBIDE-26198 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM1 > > > For JBIDE 4.9.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.9.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.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.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.1.Final > > {code} > mvn clean verify -Dtpc.version=4.80.1.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.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26198) For JBIDE 4.9.0.AM1: Prepare for 4.9.0.AM1 / 12.9.0.AM1 [central-update]

by Nick Boldt (JIRA)

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

7 years, 8 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 July 2018