[JBoss JIRA] (JBIDE-20217) JDT Debug can not connect/list VM started with suspend=y
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20217?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20217:
----------------------------------------
Fix Version/s: 4.3.0.Beta2
> 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
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> 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
[JBoss JIRA] (JBTIS-460) When editing blueprint.xml, xml snippets disappearing and changing for no apparent reason.
by Roger Hui (JIRA)
Roger Hui created JBTIS-460:
-------------------------------
Summary: When editing blueprint.xml, xml snippets disappearing and changing for no apparent reason.
Key: JBTIS-460
URL: https://issues.jboss.org/browse/JBTIS-460
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: Fuse IDE
Environment: JBoss Fuse Tooling Apache Camel Editor 7.3.0.v20150622-1435-H1-Final org.fusesource.ide.camel.editor.feature.feature.group JBoss by Red Hat
Reporter: Roger Hui
1. create new Fuse Project, select camel-archetype-cxf-contract-first
2. select blueprint.xml from src/main/resources/OSGI-INF/blueprint
3. 'Design' view is shown
4. select 'Source' tab
5. select 'Design' tab
6. select 'Source' tab
7. At this point blueprint.xml is showing that a change has been made. Further inspection shows that some of the xml has been removed. Selecting 'Design' tab again shows that some components have been deleted.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20002) Explorer: Delete multiple OpenShift resources at once
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20002?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-20002:
-------------------------------------
Assignee: (was: Jeff Cantrill)
> Explorer: Delete multiple OpenShift resources at once
> -----------------------------------------------------
>
> Key: JBIDE-20002
> URL: https://issues.jboss.org/browse/JBIDE-20002
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> It would be nice to have a feature allowing removing more resources at once:
> 1) Multiselect on some specific type of resource (e.g. pods) and deleting them via context menu "Delete resources..." which pop up dialog "Do you really want to delete selected resources?" with Yes, No, Cancel.
> 2) Deleting specific resources - from context menu on Pods / Builds etc. I would like to choose "Delete resources..." to remove all underlying resources.
> 3) Delete all resources. Should be accessible from context menu of a project.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ]
Jeff Cantrill reassigned JBDS-3434:
-----------------------------------
Assignee: Max Rydahl Andersen (was: Jeff Cantrill)
> Kubernetes editor & wizard
> --------------------------
>
> Key: JBDS-3434
> URL: https://issues.jboss.org/browse/JBDS-3434
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.x
> Reporter: Charles Moulliard
> Assignee: Max Rydahl Andersen
> Fix For: 9.0.x
>
>
> To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose :
> - a kubernetes editor within JBDS to update the YAML or JSON file and
> - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20047) As I user I want to be able to manually trigger builds
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20047?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-20047:
-------------------------------------
Assignee: (was: Jeff Cantrill)
> As I user I want to be able to manually trigger builds
> ------------------------------------------------------
>
> Key: JBIDE-20047
> URL: https://issues.jboss.org/browse/JBIDE-20047
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Fix For: 4.3.0.Beta2
>
>
> In STI a build is triggered by a change in the git repository. As a user I can thus triggered a build via a git push given that the git repo has the webhook installed. If I dont have the webhooks installed and I'm maybe not able to install them I'd like to be able to manually trigger the build.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months