May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22385) Show Console Output When Standard Out Changes toggle item is always triggered

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22385?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22385: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 > Show Console Output When Standard Out Changes toggle item is always triggered > ----------------------------------------------------------------------------- > > Key: JBIDE-22385 > URL: https://issues.jboss.org/browse/JBIDE-22385 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > Tool item Show Console Output When Standard Out Changes placed in console view of rsync output is triggerable. If it is not triggered, console view should not be shown forcefully if different console view is opened. At the moment when I am having opened 2 console views, first one with log of an application pod and another one with rsync output for a server adapter, the pod log console view is forced to display rsync output even if the tool item is in the other console view (for rsync) not triggered. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22381) Server Adapter Wizard: Enable to download project if it is not present in Eclipse workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22381?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22381: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.x) > Server Adapter Wizard: Enable to download project if it is not present in Eclipse workspace > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22381 > URL: https://issues.jboss.org/browse/JBIDE-22381 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha3 > > > If there is no project in Eclipse workspace or if there is not related project to selected OpenShift service, it is not possible/reasonable to proceed through wizard, because create server adapter would not be the desired one. It would be nice, if there would be some link/button to import an application to Eclipse workspace, like we have for OpenShift 2 (import through server adapter wizard and once imported proceed without any issues). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22327) Allow routes to be edited in server editor as they can in new server wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22327?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-22327. -------------------------------------- Fix Version/s: 4.4.0.Alpha2 Resolution: Duplicate Issue > Allow routes to be edited in server editor as they can in new server wizard > --------------------------------------------------------------------------- > > Key: JBIDE-22327 > URL: https://issues.jboss.org/browse/JBIDE-22327 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > See comments on https://github.com/jbosstools/jbosstools-openshift/pull/1149 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22327) Allow routes to be edited in server editor as they can in new server wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22327?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22327: ---------------------------------------- Assignee: Andre Dietisheim > Allow routes to be edited in server editor as they can in new server wizard > --------------------------------------------------------------------------- > > Key: JBIDE-22327 > URL: https://issues.jboss.org/browse/JBIDE-22327 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha2 > > > See comments on https://github.com/jbosstools/jbosstools-openshift/pull/1149 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22383: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 > Application Wizard: Selected project combo box is empty > ------------------------------------------------------- > > Key: JBIDE-22383 > URL: https://issues.jboss.org/browse/JBIDE-22383 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-202) Can't tune docker timeout [EBZ#494131]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-202: --------------------------------------- Summary: Can't tune docker timeout [EBZ#494131] Key: ERT-202 URL: https://issues.jboss.org/browse/ERT-202 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik reassigned JBDS-3799: --------------------------------------- Assignee: (was: Hardy Ferentschik) > Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime > ----------------------------------------------------------------------------------------- > > Key: JBDS-3799 > URL: https://issues.jboss.org/browse/JBDS-3799 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Priority: Critical > Labels: havoc > Fix For: 10.0.0.Alpha2 > > > This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272 > Is causing rsync issues such as: > default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant > There was an error when attempting to rsync a synced folder. > Please inspect the error message below for more info. > Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ > Guest path: /vagrant > Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant > Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts. > dup() in/out/err failed > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError

by Martin Malina (JIRA)

Martin Malina created JBIDE-22417: ------------------------------------- Summary: Eclipse will not run with java9 - NoClassDefFoundError Key: JBIDE-22417 URL: https://issues.jboss.org/browse/JBIDE-22417 Project: Tools (JBoss Tools) Issue Type: Bug Components: upstream Affects Versions: 4.4.0.Alpha2 Reporter: Martin Malina As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start. Java version: {code} $ java -version java version "9-ea" Java(TM) SE Runtime Environment (build 9-ea+118) Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode) {code} Error log: {code} !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241 !MESSAGE Application error !STACK 1 org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386) at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504) at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) ... 22 more Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) ... 24 more !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248 !MESSAGE FrameworkEvent ERROR !STACK 0 java.lang.NoClassDefFoundError: javax/annotation/PreDestroy at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426) at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154) at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111) at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74) at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:175) at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106) at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139) at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156) at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) at org.eclipse.osgi.container.Module.doStop(Module.java:634) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) at java.lang.Thread.run(java.base@9-ea/Thread.java:804) Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349) at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419) ... 21 more {code} Upstream issue - targeted for Neon.1: https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22318) Create JMX PoC Connection to Openshift EAP

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22318?page=com.atlassian.jira.plugi... ] Thomas Mäder updated JBIDE-22318: --------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.x) > Create JMX PoC Connection to Openshift EAP > ------------------------------------------ > > Key: JBIDE-22318 > URL: https://issues.jboss.org/browse/JBIDE-22318 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.0.Alpha3 > > > Find out what is needed to connect to an EAP instance inside an Openshift pod -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22416) Plugins dependency conflict when importing JavaEE7 Sample

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-22416: ------------------------------------- Summary: Plugins dependency conflict when importing JavaEE7 Sample Key: JBIDE-22416 URL: https://issues.jboss.org/browse/JBIDE-22416 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.4.0.Alpha1 Environment: Version: 10.0.0.Alpha1 Build id: Alpha1-v20160520-0424-B5396 Build date: 20160520-0424 Reporter: Josef Kopriva Attachments: import_issue.png When I import JavaEE7 sample sample extra/spock-tests, I cannot install plugin due to plugin conflict issue. {code:java} Cannot complete the install because of a conflicting dependency. Software being installed: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) Software currently installed: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396) Software currently installed: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423) Only one of the following can be installed at once: Java Development Tools Core 3.12.0.v20160426-1326 (org.eclipse.jdt.core 3.12.0.v20160426-1326) Java Development Tools Core 3.11.0.xx-201604081629-e45 (org.eclipse.jdt.core 3.11.0.xx-201604081629-e45) Cannot satisfy dependency: From: Red Hat Developer Studio (Core Features) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.feature.feature.group 10.0.0.Alpha1-v20160520-0424-B5396) To: org.eclipse.jdt.feature.group 0.0.0 Cannot satisfy dependency: From: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396) To: com.jboss.devstudio.core.feature.feature.group [10.0.0.Alpha1-v20160520-0424-B5396] Cannot satisfy dependency: From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201604081629-e45) To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201604081629-e45] Cannot satisfy dependency: From: Groovy-Eclipse Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) To: org.codehaus.groovy.compilerless.feature.feature.group [2.9.2.xx-201604081629-e45] Cannot satisfy dependency: From: Groovy-Eclipse Headless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.headless.feature.feature.group 2.9.2.xx-201604081629-e45) To: org.codehaus.groovy.jdt.patch.feature.group [2.9.2.xx-201604081629-e45] Cannot satisfy dependency: From: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45) To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0 Cannot satisfy dependency: From: Java Development Tools JUnit support 3.9.0.v20160421-1701 (org.eclipse.jdt.junit 3.9.0.v20160421-1701) To: bundle org.eclipse.jdt.core [3.12.0,4.0.0) Cannot satisfy dependency: From: TestNG Eclipse Support 6.9.11.201604020423 (org.testng.eclipse 6.9.11.201604020423) To: bundle org.eclipse.jdt.junit 0.0.0 Cannot satisfy dependency: From: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423) To: org.testng.eclipse [6.9.11.201604020423] Cannot satisfy dependency: From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.9.2.xx-201604081629-e45 Eclipse Java Development Tools 3.12.0.v20160428-0800 (org.eclipse.jdt.feature.group 3.12.0.v20160428-0800) To: org.eclipse.jdt.core [3.11.0.xx-201604081629-e45] {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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