April 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26609) For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [fusetools-extras]

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26609: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [fusetools-extras] Key: JBIDE-26609 URL: https://issues.jboss.org/browse/JBIDE-26609 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools-extras Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools-extras task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26608?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26608: ---------------------------------- Assignee: Lars Heinemann > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-26608 > URL: https://issues.jboss.org/browse/JBIDE-26608 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [fusetools]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26608: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [fusetools] Key: JBIDE-26608 URL: https://issues.jboss.org/browse/JBIDE-26608 Project: Tools (JBoss Tools) Issue Type: Task Components: fusetools Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [fusetools]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26607?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26607: ---------------------------------- Assignee: George Gastaldi > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [forge] > ------------------------------------------------------------------ > > Key: JBIDE-26607 > URL: https://issues.jboss.org/browse/JBIDE-26607 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [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.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26607: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [forge] Key: JBIDE-26607 URL: https://issues.jboss.org/browse/JBIDE-26607 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26606: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [central] Key: JBIDE-26606 URL: https://issues.jboss.org/browse/JBIDE-26606 Project: Tools (JBoss Tools) Issue Type: Task Components: central Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [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.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

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

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26605?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-26605: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26605 > URL: https://issues.jboss.org/browse/JBIDE-26605 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.12.0.AM1 > > > For JBIDE 4.12.0.AM1 [foundation]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.12.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

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

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26605: ---------------------------------- Summary: For JBIDE 4.12.0.AM1: Prepare for 4.12.0.AM1 / 12.12.0.AM1 [foundation] Key: JBIDE-26605 URL: https://issues.jboss.org/browse/JBIDE-26605 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Jeff MAURY Fix For: 4.12.0.AM1 For JBIDE 4.12.0.AM1 [foundation]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.12.0.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.12.0.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.12.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.11.0.Final-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26598) Unable to connect to "local" JMX process when instance launched with JDK 11

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26598?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-26598: ------------------------------------- Assignee: Ondrej Dockal > Unable to connect to "local" JMX process when instance launched with JDK 11 > --------------------------------------------------------------------------- > > Key: JBIDE-26598 > URL: https://issues.jboss.org/browse/JBIDE-26598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.11.0.Final > Reporter: Aurélien Pupier > Assignee: Ondrej Dockal > Priority: Blocker > Fix For: 4.11.0.Final > > > {code} > org.jboss.tools.jmx.local > Error > Wed Mar 27 09:25:29 CET 2019 > Unable to connect to jvm > org.jboss.tools.jmx.jvmmonitor.core.JvmCoreException: Could not get JMX service URL (PID: 9470) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:462) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.initialize(ActiveJvm.java:445) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:233) > at org.jboss.tools.jmx.jvmmonitor.internal.core.ActiveJvm.connect(ActiveJvm.java:213) > at org.jboss.tools.jmx.local.internal.JvmConnectionWrapper.connect(JvmConnectionWrapper.java:118) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 April 2019