April 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27221) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [foundation]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27221?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-27221: ------------------------------------------ bump up to parent pom version = 4.16.0.AM1-SNAPSHOT > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-27221 > URL: https://issues.redhat.com/browse/JBIDE-27221 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.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.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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 foundation 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27221) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [foundation]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27221?page=com.atlassian.jira.plug... ] Stephane Bouchet closed JBIDE-27221. ------------------------------------ Resolution: Done > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-27221 > URL: https://issues.redhat.com/browse/JBIDE-27221 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Stephane Bouchet > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.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.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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 foundation 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4826) Installer do not extract EXE file

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBDS-4826?page=com.atlassian.jira.plugin... ] Ondrej Dockal commented on JBDS-4826: ------------------------------------- I tried this again on the most similar environment I could get. windows 10 Enterprise 1909 - x64 using openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode). I still could not reproduce this issue. [~luca.preziati1] Could you please try this again using newer java? Also, can you check that codereadystudio.exe is really missing, couldn't it just be it is hidden in the directory (like try to use cli to show folder content)? Another attempt could be to let the checkbox checked at the end of installation where it asks whether to run studio just after installation is done? > Installer do not extract EXE file > ---------------------------------- > > Key: JBDS-4826 > URL: https://issues.redhat.com/browse/JBDS-4826 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.13.0.GA, 12.14.0.GA > Reporter: Luca Preziati > Priority: Blocker > Attachments: exe-missing.jpg, shared-libraries.jpg > > > The installer do not extract exe. > I extract manually from file I extract from this path the exe: codereadystudio-12.14.0.GA-installer-standalone.jar\devstudio\binary\com.jboss.devstudio.core.package.executable.win32.win32.x86_64_12.14.0.GA-v20200305-0719-B6018\ > !exe-missing.jpg|thumbnail! > But the companion shared libraries are missing. > !shared-libraries.jpg|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26878) Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26878?page=com.atlassian.jira.plug... ] Ondrej Dockal closed JBIDE-26878. --------------------------------- Verified on: 12.15.0.GA-v20200416-0717-B6249 > Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor > ------------------------------------------------------------------------------------- > > Key: JBIDE-26878 > URL: https://issues.redhat.com/browse/JBIDE-26878 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Major > Fix For: 4.15.0.Final > > > I can image improved validation of Pull secret file that is available in CRC Server wizard and Server Editor. > Missing validation of CRC Binary: > * Please select a valid CRC Binary, which would check that file is really a crc binary - we used similar validation for minishift where (I f I recall it right) we checked in process the output from `minishift version` or `minishift status` command. Something similar I can imagine to be used for crc. Since `crc status` could return different outputs, version seems to be better option. I would agree to postpone this validation once the crc is GA. then please ignore this and create new jira issue. Thanks! > I can imagine all of those validation in action for pull secret path input: > * Path does not exist > * Is not a file > * Is not executable (user cannot read the file) > * Is not a valid Pull secret file (probably check for if file's content is a valid json and/or we can probably validate if json's first object is "auths"? This would be nice, but simple json validation seems fine) > I believe that last three points could be validated at once by reading the file's content and creating valid json object, or else showing the error that given path is no valid a secret file. It's up implementation, right? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4830) For JBDS 12.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [installer]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBDS-4830?page=com.atlassian.jira.plugin... ] Stephane Bouchet commented on JBDS-4830: ---------------------------------------- bump up to parent pom version = 4.16.0.AM1-SNAPSHOT > For JBDS 12.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [installer] > ---------------------------------------------------------------------- > > Key: JBDS-4830 > URL: https://issues.redhat.com/browse/JBDS-4830 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.16.0.AM1 > > > For JBDS 12.16.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.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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 installer 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4830) For JBDS 12.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [installer]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBDS-4830?page=com.atlassian.jira.plugin... ] Stephane Bouchet closed JBDS-4830. ---------------------------------- Resolution: Done > For JBDS 12.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [installer] > ---------------------------------------------------------------------- > > Key: JBDS-4830 > URL: https://issues.redhat.com/browse/JBDS-4830 > Project: Red Hat CodeReady Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 12.16.0.AM1 > > > For JBDS 12.16.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.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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 installer 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27233) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [quarkus]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27233: ---------------------------------------- Summary: For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [quarkus] Key: JBIDE-27233 URL: https://issues.redhat.com/browse/JBIDE-27233 Project: Tools (JBoss Tools) Issue Type: Task Components: quarkus Reporter: Stephane Bouchet Fix For: 4.16.0.AM1 For JBIDE 4.16.0.AM1 [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.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.16.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.16.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.15.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.15.0.Final-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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27233) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [quarkus]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27233?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27233: ---------------------------------------- Assignee: Jeff MAURY > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [quarkus] > -------------------------------------------------------------------- > > Key: JBIDE-27233 > URL: https://issues.redhat.com/browse/JBIDE-27233 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: quarkus > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.0.AM1 [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.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27234) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [webservices]

by Stephane Bouchet (Jira)

Stephane Bouchet created JBIDE-27234: ---------------------------------------- Summary: For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [webservices] Key: JBIDE-27234 URL: https://issues.redhat.com/browse/JBIDE-27234 Project: Tools (JBoss Tools) Issue Type: Task Components: webservices Reporter: Stephane Bouchet Fix For: 4.16.0.AM1 For JBIDE 4.16.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.16.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.16.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.16.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.15.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.15.0.Final-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 webservices 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27234) For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [webservices]

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27234?page=com.atlassian.jira.plug... ] Stephane Bouchet reassigned JBIDE-27234: ---------------------------------------- Assignee: Jeff MAURY > For JBIDE 4.16.0.AM1: Prepare for 4.16.0.AM1 / 12.16.0.AM1 [webservices] > ------------------------------------------------------------------------ > > Key: JBIDE-27234 > URL: https://issues.redhat.com/browse/JBIDE-27234 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.16.0.AM1 > > > For JBIDE 4.16.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.16.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.16.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.16.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.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.15.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.15.0.Final-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 webservices 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)

4 years, 5 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 April 2020