April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24217: ------------------------------- Fix Version/s: 4.4.4.Final > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Fix For: 4.4.4.Final > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24217: ---------------------------------- Assignee: Jeff MAURY > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24138) Implement queryMbeans for Jolokia

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24138?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24138: ----------------------------------------- i need to wait for new TP for Fuse Tooling [FUSETOOLS-2355] to verify it correctly but for that I need the [wtp bug|https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793] to be fixed and integrated in [JBoss Tools|JBIDE-24240] > Implement queryMbeans for Jolokia > --------------------------------- > > Key: JBIDE-24138 > URL: https://issues.jboss.org/browse/JBIDE-24138 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.4.4.AM1 > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.4.4.AM3 > > > Currently JolokiaMBeanServerConnection.queryMBeans is not implemented > @Override > public Set<ObjectInstance> queryMBeans(ObjectName name, QueryExp query) throws IOException { > // TODO Auto-generated method stub > return null; > } -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24145) Command to tune memory requirements for a deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24145?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24145: ------------------------------- Summary: Command to tune memory requirements for a deployment (was: Command to tune memory requirements for a deployement) > Command to tune memory requirements for a deployment > ---------------------------------------------------- > > Key: JBIDE-24145 > URL: https://issues.jboss.org/browse/JBIDE-24145 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4360) Could not load repository template extension contributed by 'org.eclipse.mylyn.bugzilla.ide' with connectorKind 'bugzilla'

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4360: ---------------------------------- Summary: Could not load repository template extension contributed by 'org.eclipse.mylyn.bugzilla.ide' with connectorKind 'bugzilla' Key: JBDS-4360 URL: https://issues.jboss.org/browse/JBDS-4360 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: central Affects Versions: 10.4.0.AM3 Environment: Devstudio-10.4.0.AM3-v20170410-1340-B413 installed via jar installer Reporter: Lukáš Valach Assignee: Nick Boldt Fix For: 10.4.0.AM3 Attachments: Devstudio_ConnectorKind_bugzilla.log After installation of Spring IDE from RH Central I got this error: {code} !ENTRY org.eclipse.mylyn.tasks.core 4 0 2017-04-11 11:21:28.715 !MESSAGE Unexpected error while loading repository template extensions !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2017-04-11 11:21:28.715 !MESSAGE Could not load repository template extension contributed by 'org.eclipse.mylyn.bugzilla.ide' with connectorKind 'bugzilla' log4j:WARN No appenders could be found for logger (org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob). log4j:WARN Please initialize the log4j system properly. !ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2017-04-11 11:21:50.950 !MESSAGE No repository found at file:/home/lvalach/JBDS/devstudio-10.4.0.AM3-v20170406-1058-B390-installer-standalone/studio/configuration/org.eclipse.osgi/368/data/listener_1925729951/. {code} The similar problem has been reported in JBIDE-23833 and in JBDS-2696. I also noticed that this NPE appeared in the log during the installation: {code} !ENTRY org.eclipse.equinox.p2.core 4 0 2017-04-11 11:47:38.199 !MESSAGE Exception during event notification !STACK 0 java.lang.NullPointerException at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdater.sameProfile(AutomaticUpdater.java:76) at org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdater$1.notify(AutomaticUpdater.java:63) at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:108) at org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) {code} This problem appears in devstudio-10.4.0.AM3-v20170410-1340-B413 installed using jar installer. I can't reproduce the this problem in Neon3 + JBT (Abridged). It seems that this problem can be resolved by installation of "Mylyn Issue Tracker Connectors" form RH Central. Maybe we should put Mylyn connector as dependency of Spring IDE? Eclipse log (installation of Spring IDE + start after installation): [^Devstudio_ConnectorKind_bugzilla.log] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4358) include EAP 7.1 in devstudio 11 installer?

by Tim Moran (JIRA)

[ https://issues.jboss.org/browse/JBDS-4358?page=com.atlassian.jira.plugin.... ] Tim Moran commented on JBDS-4358: --------------------------------- EAP 7.1 is marked off track and they anticipate to have a replanning done by Easter. While I would normally +1 it, I don't think it will be ready and available by the end of July. I am going to give a "=" until [~jpallich] can help get us a better idea of what their schedule looks like. Side note, is a 1 week window enough time for us? > include EAP 7.1 in devstudio 11 installer? > ------------------------------------------ > > Key: JBDS-4358 > URL: https://issues.jboss.org/browse/JBDS-4358 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, installer, server, upstream > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.AM1 > > > EAP 7.1.0 is due at the end of July 2017 (1 week before devstudio 11.0.0.GA is complete). > There will also be a public beta starting early June 2017 (during the devstudio 11.0.0.AM1 sprint), giving us lots of time to provide feedback to from Server Tools to EAP. > As such we should decide if we want to include that in the devstudio/devsuite installers, or stick with EAP 7.0.0 until a later 11.x release. > [~jeffmaury] [~mbenitez] [~tim.moran] [~jpallich] please vote +1 or -1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24129) download-devstudio profile breaks component builds

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24129?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24129: ------------------------------------ I took the 2) approach when providing the PR for webservices. The goal for having the itests into the component repo is to have the dev team write itests with new features and having to download DevStudio would be counter-productive. So I'm more 2) oriented even if it requires more attention in the beginning. > download-devstudio profile breaks component builds > -------------------------------------------------- > > Key: JBIDE-24129 > URL: https://issues.jboss.org/browse/JBIDE-24129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.4.AM2 > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.4.AM3 > > > We have used download-devstudio profile to run the integration tests against full devstudio in the past. This stopped working recently. > {code} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 > [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 10.4.0.v20170324-0935 requires 'org.jboss.ide.eclipse.as.feature.feature.group [3.2.4.v20170315-1707]' but it could not be found > [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 10.4.0.v20170324-0935 depends on: com.jboss.devstudio.core.rpm.feature.feature.group [10.4.0.v20170324-0935] > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.as.plugins:org.jboss.ide.eclipse.as.dmr:3.2.4-SNAPSHOT @ /Users/psrna/GitHub/jbosstools-server/as/plugins/org.jboss.ide.eclipse.as.dmr/pom.xml: See log for details -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4181) No valid JDK found

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-4181. ------------------------------- Nothing to be done here. Closing. > No valid JDK found > ------------------ > > Key: JBDS-4181 > URL: https://issues.jboss.org/browse/JBDS-4181 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: common, upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode) > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 10.4.0.AM2 > > > When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log > {code} > java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs. > java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs. > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23872. --------------------------------- Verified in JBoss Tools 4.4.4.AM2. Now even after the republish there is the same amount of files and the web page works. > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Assignee: Rob Stryker > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > Attachments: publish.log > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24074) Download runtimes eap-6.2 has bad layout on credential page

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24074?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24074. --------------------------------- I'm not sure what was wrong exactly. But I have verified that it works correctly for me in JBT 4.4.4.AM2. > Download runtimes eap-6.2 has bad layout on credential page > ----------------------------------------------------------- > > Key: JBIDE-24074 > URL: https://issues.jboss.org/browse/JBIDE-24074 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.4.4.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > Very ugly layout. The edit button exists when it should not exist, and it breaks the entire layout. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 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 April 2017