July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20202) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Base]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20202?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20202: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Base] > -------------------------------------------------------------------------------- > > Key: JBIDE-20202 > URL: https://issues.jboss.org/browse/JBIDE-20202 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core, usage > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Base]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20205) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20205?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20205: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JavaEE] > ---------------------------------------------------------------------------------- > > Key: JBIDE-20205 > URL: https://issues.jboss.org/browse/JBIDE-20205 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [JavaEE]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20206) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20206?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20206: -------------------------------------- Assignee: Alexey Kazakov > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [JST] > ------------------------------------------------------------------------------- > > Key: JBIDE-20206 > URL: https://issues.jboss.org/browse/JBIDE-20206 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [JST]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20065) hibernate util.invoke* silently swallows NoSuchMethod

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20065?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-20065. ------------------------------- Assignee: Koen Aers Resolution: Done > hibernate util.invoke* silently swallows NoSuchMethod > ----------------------------------------------------- > > Key: JBIDE-20065 > URL: https://issues.jboss.org/browse/JBIDE-20065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta2 > > > as seen in JBIDE-20042 errors are swalloed (just logged) meaning many methods to hibernate just returns null resulting in broken logic. > Example: https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... > why are these not turned into actual RuntimeExceptions and raised ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20065) hibernate util.invoke* silently swallows NoSuchMethod

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20065?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-20065: ----------------------------------- I had to rework some of the tests to account for this and I also found (and corrected) some glitches that were caused by this. > hibernate util.invoke* silently swallows NoSuchMethod > ----------------------------------------------------- > > Key: JBIDE-20065 > URL: https://issues.jboss.org/browse/JBIDE-20065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.3.0.Beta2 > > > as seen in JBIDE-20042 errors are swalloed (just logged) meaning many methods to hibernate just returns null resulting in broken logic. > Example: https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... > why are these not turned into actual RuntimeExceptions and raised ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19706) Refactor the hibernate service provider implementations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19706?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-19706: ----------------------------------- The service implementation classes (ServiceImpl) still need to be refactored but this will happen later. I'll open a separate issue for this. > Refactor the hibernate service provider implementations > -------------------------------------------------------- > > Key: JBIDE-19706 > URL: https://issues.jboss.org/browse/JBIDE-19706 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta2 > > > The SPI implementation "proxy" classes need a common superclass that can implement most of the functionality using introspection. In this way probably 70% of the code can be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19706) Refactor the hibernate service provider implementations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19706?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-19706. ------------------------------- Resolution: Done > Refactor the hibernate service provider implementations > -------------------------------------------------------- > > Key: JBIDE-19706 > URL: https://issues.jboss.org/browse/JBIDE-19706 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Beta2 > > > The SPI implementation "proxy" classes need a common superclass that can implement most of the functionality using introspection. In this way probably 70% of the code can be eliminated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20216) Include Mylyn Wikitext Asciidoc editor in JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20216?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20216: ------------------------------- Description: Wiki page: https://wiki.eclipse.org/Mylyn/WikiText/AsciiDoc Update site: http://download.eclipse.org/mylyn/snapshots/nightly/docs/ (wikitext-extra) Features to include: * org.eclipse.mylyn.wikitext.extras * org.eclipse.mylyn.wikitext_feature (already in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... [ see JBDS-3259 ] TODO: pull a mirror: http://download.jboss.org/jbosstools/updates/requirements/mylyn-extras/2.... (done) TODO: add it to JBT/JBDS TP TODO: add asciidoctor plugin (not whole feature) to CoreTools for JBT/JBDS TODO? add new connector to JBT/JBDS Central? Early Access? TODO? add to JBDS BYOE feature https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... TODO? add to Central/Marketplace requires a feature wrapper, or just use org.eclipse.mylyn.wikitext.extras feature TODO: @max to look at other plugins in org.eclipse.mylyn.wikitext.extras feature to see if anything is "scary" was: Wiki page: https://wiki.eclipse.org/Mylyn/WikiText/AsciiDoc Update site: http://download.eclipse.org/mylyn/snapshots/nightly/docs/ (wikitext-extra) Features to include: * org.eclipse.mylyn.wikitext.extras * org.eclipse.mylyn.wikitext_feature (already in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... [ see JBDS-3259 ] TODO: pull a mirror and add it to: JBT/JBDS TP TODO: add asciidoctor plugin (not whole feature) to CoreTools for JBT/JBDS TODO? add new connector to JBT/JBDS Central? Early Access? TODO? add to JBDS BYOE feature https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... TODO? add to Central/Marketplace requires a feature wrapper, or just use org.eclipse.mylyn.wikitext.extras feature TODO: @max to look at other plugins in org.eclipse.mylyn.wikitext.extras feature to see if anything is "scary" > Include Mylyn Wikitext Asciidoc editor in JBT/JBDS > -------------------------------------------------- > > Key: JBIDE-20216 > URL: https://issues.jboss.org/browse/JBIDE-20216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.CR1 > > > Wiki page: https://wiki.eclipse.org/Mylyn/WikiText/AsciiDoc > Update site: http://download.eclipse.org/mylyn/snapshots/nightly/docs/ (wikitext-extra) > Features to include: > * org.eclipse.mylyn.wikitext.extras > * org.eclipse.mylyn.wikitext_feature (already in TP: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.50.x/jbo... [ see JBDS-3259 ] > TODO: pull a mirror: http://download.jboss.org/jbosstools/updates/requirements/mylyn-extras/2.... (done) > TODO: add it to JBT/JBDS TP > TODO: add asciidoctor plugin (not whole feature) to CoreTools for JBT/JBDS > TODO? add new connector to JBT/JBDS Central? Early Access? > TODO? add to JBDS BYOE feature https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > TODO? add to Central/Marketplace requires a feature wrapper, or just use org.eclipse.mylyn.wikitext.extras feature > TODO: @max to look at other plugins in org.eclipse.mylyn.wikitext.extras feature to see if anything is "scary" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20217) JDT Debug can not connect/list VM started with suspend=y

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20217?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20217: -------------------------------------- Assignee: Rob Stryker > JDT Debug can not connect/list VM started with suspend=y > -------------------------------------------------------- > > Key: JBIDE-20217 > URL: https://issues.jboss.org/browse/JBIDE-20217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Rob Stryker > > Having a VM started with suspend=y cause the following error to be logged from https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... due to Exception thrown in ToolsCore.getJvmArgs > Seemingly JVMStat can not connect to a suspended VM. > {code} > eclipse.buildId=4.5.0.I20150603-2000 > java.version=1.8.0_45 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Command-line arguments: -os linux -ws gtk -arch x86_64 > org.jboss.tools.common.jdt.debug > Error > Wed Jul 08 17:16:00 CEST 2015 > {code} > {code} > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > ... 14 more > Root exception: > sun.jvmstat.monitor.MonitorException: Could not synchronize with target > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) > at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) > at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) > at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) > at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) > at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) > at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) > at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20217) JDT Debug can not connect/list VM started with suspend=y

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20217: ------------------------------------- Summary: JDT Debug can not connect/list VM started with suspend=y Key: JBIDE-20217 URL: https://issues.jboss.org/browse/JBIDE-20217 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Beta1 Reporter: Aslak Knutsen Having a VM started with suspend=y cause the following error to be logged from https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... due to Exception thrown in ToolsCore.getJvmArgs Seemingly JVMStat can not connect to a suspended VM. {code} eclipse.buildId=4.5.0.I20150603-2000 java.version=1.8.0_45 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86_64 org.jboss.tools.common.jdt.debug Error Wed Jul 08 17:16:00 CEST 2015 {code} {code} java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: sun.jvmstat.monitor.MonitorException: Could not synchronize with target at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) ... 14 more Root exception: sun.jvmstat.monitor.MonitorException: Could not synchronize with target at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.synchWithTarget(PerfDataBuffer.java:277) at sun.jvmstat.perfdata.monitor.v2_0.PerfDataBuffer.buildMonitorMap(PerfDataBuffer.java:131) at sun.jvmstat.perfdata.monitor.PerfDataBufferImpl.findByName(PerfDataBufferImpl.java:241) at sun.jvmstat.perfdata.monitor.AbstractPerfDataBuffer.findByName(AbstractPerfDataBuffer.java:100) at sun.jvmstat.perfdata.monitor.AbstractMonitoredVm.findByName(AbstractMonitoredVm.java:85) at sun.jvmstat.monitor.MonitoredVmUtil.jvmArgs(MonitoredVmUtil.java:145) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getJvmArgs(Tools.java:780) at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getJvmArgs(ToolsCore.java:98) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModelsUsingTools(RemoteDebugActivator.java:166) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModel(RemoteDebugActivator.java:145) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getVmModels(RemoteDebugActivator.java:132) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:193) at org.jboss.tools.common.jdt.debug.RemoteDebugActivator.getDebugModels(RemoteDebugActivator.java:227) at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator.discoverRemoteApplication(RemoteDebugUIActivator.java:137) at org.jboss.tools.common.jdt.debug.ui.RemoteDebugUIActivator$1.run(RemoteDebugUIActivator.java:93) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 2015