[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-22152 at 6/3/16 1:35 PM:
------------------------------------------------------------
OK, I tested it and the difference with a simple Java debug session is that it is not possible to remove it whereas a Java program can be removed even after the debug conf has been deleted.
Checking why remove is not enabled in our case
was (Author: jeffmaury):
OK, I tested it and the difference with a simple Java debug session is that it is not possible to remove it whereas a Java program can be removed even after the debug conf has been deleted.
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-22152:
------------------------------------
OK, I tested it and the difference with a simple Java debug session is that it is not possible to remove it whereas a Java program can be removed even after the debug conf has been deleted.
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBTIS-729) Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-729?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-729:
----------------------------------
*Reason:* Pull in org.eclipse.core.runtime.compatibility and resync with 4.4.0.Final JBT
*Project page/sources:*
*Version:* 4.4.0.Alpha1-SNAPSHOT
*License and owner:* EPL
*Original p2 repo:*
*JBoss mirror:*
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS components
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
< org.jboss.tools.common [3.8.0.Alpha1-v20160511-2035-B942]
< org.jboss.tools.community.project.examples [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.community.central [2.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.as.test.core [3.2.0.Alpha1-v20160519-0029-B970]
< org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.tests [3.7.0.Alpha1-v20160511-2035-B942]
< org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.community.central.feature.feature.jar [2.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.project.examples.feature.feature.group [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.common.base.test [3.8.0.Alpha1-v20160511-2035-B942]
< org.jboss.tools.common.test [3.8.0.Alpha1-v20160511-2035-B942]
< org.jboss.tools.project.examples [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.jmx.core.test [1.8.0.Alpha1-v20160519-0029-B970]
< org.jboss.tools.project.examples.cheatsheet [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.community.central.feature.feature.group [2.1.0.Alpha1-v20160510-1913-B866]
> org.jboss.tools.community.project.examples [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.community.central [2.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.common.test [3.8.0.Final-v20160603-0250-B985]
> org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.as.test.core [3.2.0.Final-v20160603-0300-B1005]
> org.jboss.tools.common.base.test [3.8.0.Final-v20160603-0250-B985]
> org.jboss.tools.project.examples [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.jmx.core.test [1.8.0.Final-v20160603-0300-B1005]
> org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.tests [3.7.0.Final-v20160603-0250-B985]
> org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.common [3.8.0.Final-v20160603-0250-B985]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs
< org.eclipse.ocl.common [1.4.0.v20160105-1130]
< org.eclipse.ocl.uml.feature.jar [5.2.0.v20160224-1849]
< org.eclipse.ocl.feature.group [3.6.0.v20160224-1849]
< org.eclipse.uml2.uml.profile.standard [1.0.100.v20160502-0821]
< org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160502-0821]
< org.eclipse.uml2.uml.validation [5.0.0.v20160502-0821]
< org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160502-0821]
< org.eclipse.ocl.all.feature.group [5.2.0.v20160224-1849]
< org.eclipse.ocl.uml.feature.group [5.2.0.v20160224-1849]
< org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160502-0821]
< org.eclipse.uml2.codegen.ecore.ui.feature.group [2.2.0.v20160502-0821]
< org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.uml2.ant [1.0.0.v20160502-0821]
< org.jboss.tools.common.base.test [3.8.0.Alpha1-v20160511-2035-B942]
< org.eclipse.uml2.uml.ecore.importer [3.1.0.v20160502-0821]
< org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160502-0821]
< org.eclipse.emf.compare.ide.ui.feature.jar [3.2.0.201604280603]
< org.jboss.tools.as.test.core [3.2.0.Alpha1-v20160519-0029-B970]
< org.eclipse.emf.compare.rcp [2.4.0.201604280603]
< org.eclipse.emf.compare.ide [3.3.0.201604280603]
< org.eclipse.uml2.uml.edit.feature.group [5.2.0.v20160502-0821]
< org.eclipse.ocl.all.feature.jar [5.2.0.v20160224-1849]
< org.jboss.tools.project.examples [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.project.examples.cheatsheet [3.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.uml2.common [2.1.0.v20160502-0821]
< org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.2.0.v20160502-0821]
< org.eclipse.uml2.codegen.ecore [2.2.0.v20160502-0821]
< org.eclipse.uml2.uml.resources [5.2.0.v20160502-0821]
< org.eclipse.ocl [3.6.0.v20160224-1849]
< org.eclipse.emf.compare.feature.group [3.2.0.201604280603]
< org.eclipse.emf.compare.feature.jar [3.2.0.201604280603]
< org.eclipse.ocl.ecore [3.6.0.v20160224-1849]
< org.eclipse.uml2.common.edit [2.1.0.v20160502-0821]
< org.jboss.tools.community.project.examples [3.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.emf.compare.ide.ui.feature.group [3.2.0.201604280603]
< org.eclipse.emf.compare.ide.ui [4.2.0.201604280603]
< org.eclipse.emf.compare [3.3.0.201604280603]
< org.jboss.tools.jmx.core.test [1.8.0.Alpha1-v20160519-0029-B970]
< org.eclipse.uml2.uml.feature.jar [5.2.0.v20160502-0821]
< org.eclipse.uml2.uml.editor [5.2.0.v20160502-0821]
< org.jboss.tools.project.examples.feature.feature.group [3.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.uml2.types [2.0.0.v20160502-0821]
< org.jboss.tools.community.central [2.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.emf.compare.rcp.ui [4.2.0.201604280603]
< org.jboss.tools.common [3.8.0.Alpha1-v20160511-2035-B942]
< org.eclipse.uml2.common.feature.jar [2.1.0.v20160502-0821]
< org.eclipse.ocl.feature.jar [3.6.0.v20160224-1849]
< org.eclipse.uml2.common.feature.group [2.1.0.v20160502-0821]
< org.eclipse.uml2.uml [5.2.0.v20160502-0821]
< org.hamcrest.library [1.3.0.v201305281000]
< org.eclipse.emf.compare.edit [4.2.0.201604280603]
< org.eclipse.uml2.feature.jar [5.2.0.v20160502-0821]
< org.eclipse.uml2.uml.edit [5.1.100.v20160502-0821]
< org.eclipse.uml2 [5.2.0.v20160502-0821]
< org.jboss.tools.community.central.feature.feature.group [2.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.emf.compare.doc [3.2.0.201604280603]
< org.eclipse.ocl.uml [5.2.0.v20160224-1849]
< org.jboss.tools.common.test [3.8.0.Alpha1-v20160511-2035-B942]
< org.jboss.tools.tests [3.7.0.Alpha1-v20160511-2035-B942]
< org.eclipse.uml2.uml.feature.group [5.2.0.v20160502-0821]
< org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Alpha1-v20160510-1913-B866]
< org.jboss.tools.community.central.feature.feature.jar [2.1.0.Alpha1-v20160510-1913-B866]
< org.eclipse.uml2.feature.group [5.2.0.v20160502-0821]
< org.eclipse.uml2.uml.edit.feature.jar [5.2.0.v20160502-0821]
> org.eclipse.uml2.uml.ecore.importer [3.1.0.v20160516-0939]
> org.eclipse.emf.compare.ide [3.3.0.201605241249]
> org.eclipse.uml2.uml.ecore.exporter [3.0.0.v20160516-0939]
> org.jboss.tools.community.central.feature.feature.jar [2.1.0.Final-v20160603-0539-B896]
> org.eclipse.uml2.common.edit.feature.group [2.1.0.v20160516-0939]
> org.eclipse.uml2.uml.validation [5.0.0.v20160516-0939]
> org.eclipse.emf.compare.edit [4.2.0.201605241249]
> org.eclipse.uml2.common [2.1.0.v20160516-0939]
> org.jboss.tools.as.test.core [3.2.0.Final-v20160603-0300-B1005]
> org.eclipse.emf.compare.ide.ui.feature.jar [3.2.0.201605241249]
> org.eclipse.ocl.all.feature.group [5.2.0.v20160521-2033]
> org.jboss.tools.common [3.8.0.Final-v20160603-0250-B985]
> org.eclipse.ocl.all.feature.jar [5.2.0.v20160521-2033]
> org.eclipse.emf.compare.rcp.ui [4.2.0.201605241249]
> org.eclipse.uml2.uml.feature.group [5.2.0.v20160516-0939]
> org.jboss.tools.project.examples.cheatsheet [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.emf.compare.rcp [2.4.0.201605241249]
> org.jboss.tools.tests [3.7.0.Final-v20160603-0250-B985]
> org.eclipse.uml2.uml.profile.standard [1.0.100.v20160516-0939]
> org.jboss.tools.community.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.ocl.feature.jar [3.6.0.v20160521-2033]
> org.eclipse.emf.compare [3.3.0.201605241249]
> org.eclipse.uml2.common.edit.feature.jar [2.1.0.v20160516-0939]
> org.jboss.tools.community.central.feature.feature.group [2.1.0.Final-v20160603-0539-B896]
> org.eclipse.uml2.feature.group [5.2.0.v20160516-0939]
> org.jboss.tools.jmx.core.test [1.8.0.Final-v20160603-0300-B1005]
> org.eclipse.emf.compare.ide.ui.feature.group [3.2.0.201605241249]
> org.jboss.tools.project.examples.feature.feature.jar [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.ocl.common [1.4.0.v20160521-2033]
> org.jboss.tools.project.examples [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.ocl.uml.feature.group [5.2.0.v20160521-2033]
> org.eclipse.uml2 [5.2.0.v20160516-0939]
> org.eclipse.uml2.ant [1.0.0.v20160516-0939]
> org.jboss.tools.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.uml2.common.feature.group [2.1.0.v20160516-0939]
> org.jboss.tools.community.project.examples [3.1.0.Final-v20160603-0539-B896]
> org.eclipse.uml2.types [2.0.0.v20160516-0939]
> org.eclipse.ocl.uml [5.2.0.v20160521-2033]
> org.eclipse.uml2.uml.feature.jar [5.2.0.v20160516-0939]
> org.eclipse.uml2.uml.edit.feature.jar [5.2.0.v20160516-0939]
> org.eclipse.uml2.common.edit [2.1.0.v20160516-0939]
> org.eclipse.uml2.codegen.ecore [2.2.0.v20160516-0939]
> org.hamcrest.library [1.3.0.v201505072020]
> org.eclipse.emf.compare.ide.ui [4.2.0.201605241249]
> org.eclipse.uml2.uml.edit [5.1.100.v20160516-0939]
> org.eclipse.uml2.codegen.ecore.ui.feature.jar [2.2.0.v20160516-0939]
> org.eclipse.emf.compare.feature.jar [3.2.0.201605241249]
> org.eclipse.uml2.uml.edit.feature.group [5.2.0.v20160516-0939]
> org.eclipse.ocl.uml.feature.jar [5.2.0.v20160521-2033]
> org.eclipse.ocl [3.6.0.v20160521-2033]
> org.eclipse.uml2.feature.jar [5.2.0.v20160516-0939]
> org.eclipse.uml2.uml.resources [5.2.0.v20160516-0939]
> org.eclipse.uml2.uml [5.2.0.v20160516-0939]
> org.jboss.tools.common.test [3.8.0.Final-v20160603-0250-B985]
> org.eclipse.ocl.feature.group [3.6.0.v20160521-2033]
> org.eclipse.emf.compare.feature.group [3.2.0.201605241249]
> org.eclipse.uml2.common.feature.jar [2.1.0.v20160516-0939]
> org.jboss.tools.community.central [2.1.0.Final-v20160603-0539-B896]
> org.eclipse.uml2.uml.editor [5.2.0.v20160516-0939]
> org.eclipse.emf.compare.doc [3.2.0.201605241249]
> org.eclipse.ocl.ecore [3.6.0.v20160521-2033]
> org.eclipse.core.runtime.compatibility [3.2.300.v20150423-0821]
> org.jboss.tools.community.project.examples.feature.feature.group [3.1.0.Final-v20160603-0539-B896]
> org.jboss.tools.common.base.test [3.8.0.Final-v20160603-0250-B985]
> org.eclipse.uml2.codegen.ecore.ui.feature.group [2.2.0.v20160516-0939]
> org.eclipse.uml2.codegen.ecore.ui [2.1.0.v20160516-0939]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 65 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 66 unique IUs
{code}
> Teiid Designer depends on bundle in JBT/devstudio TP which no longer exists
> ---------------------------------------------------------------------------
>
> Key: JBTIS-729
> URL: https://issues.jboss.org/browse/JBTIS-729
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform, teiid
> Affects Versions: 4.4.0.Alpha1-TP, 4.4.0.Alpha1
> Reporter: Nick Boldt
>
> org.eclipse.core.runtime.compatibility was removed from the JBT and devstudio target platforms because nothing in JBT/devstudio requires it any more.
> As a result, when you try to install Teiid Designer into the staged JBT 4.4.0.Final or devstudio 10.0.0.GA via Central, you get this error:
> {code}
> !MESSAGE Missing requirement: Teiid DataTools Connectivity 10.0.0.Beta3-v20160218-1807-B4076 (org.teiid.datatools.connectivity.feature.feature.group 10.0.0.Beta3-v20160218-1807-B4076) requires 'org.eclipse.core.runtime.compatibility [3.2.200,4.0.0)' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22436) Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22436?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-22436:
---------------------------------------
[~nziakova], what JBDS/JBT did you use?
> Intermittent NullPointerException upon opening helloworld, kitchensink cheat sheets in JBDS
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-22436
> URL: https://issues.jboss.org/browse/JBIDE-22436
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Michal Jurc
> Assignee: Snjezana Peco
> Fix For: 4.4.x
>
> Attachments: helloworld-cheatsheet.xml, JBIDE-22436-9.1-helloworld.log, kitchensink-cheatsheet.xml, org.jboss.tools.cheatsheet.test.zip
>
>
> After finishing the import of {{helloworld}} and {{kitchensink}} quickstarts, the user is prompted whether the cheat sheet for the project should be opened. Upon opening it, JBDS 9.0 and 9.1 produces the following error message:
> {quote}An error has occurred. See error log for more details.
> java.lang.NullPointerException{quote}
> The detailed error log produces the same message.
> The quickstarts and their cheat sheets work even after the prompt with NullPointerException message.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months