September 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26361) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [forge]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26361: ---------------------------------- Summary: For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [forge] Key: JBIDE-26361 URL: https://issues.jboss.org/browse/JBIDE-26361 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Nick Boldt Priority: Blocker Fix For: 4.9.0.Final For JBIDE 4.9.0.Final [forge]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.9.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.9.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-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 forge 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26361) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [forge]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26361?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26361: ---------------------------------- Assignee: George Gastaldi > For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26361 > URL: https://issues.jboss.org/browse/JBIDE-26361 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Nick Boldt > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.9.0.Final > > > For JBIDE 4.9.0.Final [forge]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.9.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-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 forge 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26359) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26359: ---------------------------------- Summary: For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation] Key: JBIDE-26359 URL: https://issues.jboss.org/browse/JBIDE-26359 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Nick Boldt Priority: Blocker Fix For: 4.9.0.Final For JBIDE 4.9.0.Final [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.9.0.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.9.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26359) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26359?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26359: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26359 > URL: https://issues.jboss.org/browse/JBIDE-26359 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.9.0.Final > > > For JBIDE 4.9.0.Final [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.9.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26360) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [central]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26360: ---------------------------------- Summary: For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [central] Key: JBIDE-26360 URL: https://issues.jboss.org/browse/JBIDE-26360 Project: Tools (JBoss Tools) Issue Type: Task Components: central Reporter: Nick Boldt Priority: Blocker Fix For: 4.9.0.Final For JBIDE 4.9.0.Final [central]: 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.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.9.0.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.9.0.AM3-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 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26359) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26359?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26359: ------------------------------------ bump up to parent pom version = 4.9.0.Final-SNAPSHOT > For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26359 > URL: https://issues.jboss.org/browse/JBIDE-26359 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.9.0.Final > > > For JBIDE 4.9.0.Final [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.9.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26359) For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26359?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-26359. ------------------------------ Resolution: Done > For JBIDE 4.9.0.Final: Prepare for 4.9.0.Final / 12.9.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26359 > URL: https://issues.jboss.org/browse/JBIDE-26359 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.9.0.Final > > > For JBIDE 4.9.0.Final [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.9.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.9.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.9.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.9.0.AM3-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.9.0.AM3-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.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4642: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 12.x > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25050: ------------------------------- Fix Version/s: 4.9.x (was: 4.9.0.AM3) > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.9.x > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25050: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.x* > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.9.x > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 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 September 2018