April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4303) Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4303?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-4303. --------------------------------- Resolution: Done > Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos) > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4303 > URL: https://issues.jboss.org/browse/JBDS-4303 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 10.4.0.AM2 > > > Current implementation shows errors and warning under item selected for installation. > See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. > Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install. > If Virtualization firmware status cannot be detected (windows 7) message should say: > * Make sure hardware virtualization is enabled on your platform if supported to improve performance. > if Hardware Virtualization is Disabled: > * Please enable hardware virtualization for your platform to improve performance > If Hardware Virtualization is Enabled, no message is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1083) Integration tooling now criticizing SwitchYard quickstarts (previously ok)

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1083?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBTIS-1083: ------------------------------------------ Will look into this in the morning. > Integration tooling now criticizing SwitchYard quickstarts (previously ok) > -------------------------------------------------------------------------- > > Key: JBTIS-1083 > URL: https://issues.jboss.org/browse/JBTIS-1083 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 10.2.0.GA > Environment: DevStudioIS v 10.2, used with Fuse 6.3 > Reporter: Rick Wagner > Assignee: Brian Fitzpatrick > > Importing the 'camel-service' quickstart results in this error: > "Unspecified Camel Route Class: "JavaDSLBuilder" component is implemented as a Java Camel Route, but no class is specified." > The project will build when maven is invoked, the IDE is raising a 'false alarm'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1083) Integration tooling now criticizing SwitchYard quickstarts (previously ok)

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1083?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick reassigned JBTIS-1083: ---------------------------------------- Assignee: Brian Fitzpatrick > Integration tooling now criticizing SwitchYard quickstarts (previously ok) > -------------------------------------------------------------------------- > > Key: JBTIS-1083 > URL: https://issues.jboss.org/browse/JBTIS-1083 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 10.2.0.GA > Environment: DevStudioIS v 10.2, used with Fuse 6.3 > Reporter: Rick Wagner > Assignee: Brian Fitzpatrick > > Importing the 'camel-service' quickstart results in this error: > "Unspecified Camel Route Class: "JavaDSLBuilder" component is implemented as a Java Camel Route, but no class is specified." > The project will build when maven is invoked, the IDE is raising a 'false alarm'. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22578: -------------------------------- Fix Version/s: LATER (was: 4.5.0.Final) > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Critical > Fix For: LATER > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22578: ------------------------------------- Can't seem to reproduce for now but I don't want to close it > Publishing sometimes recursively deletes parent to deploy directory > ------------------------------------------------------------------- > > Key: JBIDE-22578 > URL: https://issues.jboss.org/browse/JBIDE-22578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Final > Environment: Eclipse Mars.2 Release (4.5.2) > Java 1.8.0_91 > Windows 7 64-bit > JBoss EAP 6.4.0 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Priority: Critical > Fix For: LATER > > Attachments: jboss_deployment.jpg, jboss_tools.20160630.stdout.log, servers.xml > > > For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it. > It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools. > We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx). > Our workspaces are structured as follows: > {noformat} > WORKSPACEROOT=$DEVROOT\workspacename > # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server > $WORKSPACEROOT\deploy > # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling > $WORKSPACEROOT\src > # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/data > # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments > $WORKSPACEROOT/server/tmp > {noformat} > The Server is configured to "Automatically publish when resources change". > What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT. > The eclipse log includes the following: > {noformat} > !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problems occurred refreshing resources > !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795 > !MESSAGE Problem finding next change, code: 5 > !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207 > !MESSAGE Incremental publish failed for module $MODULENAME > !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207 > !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process. > {noformat} > Any idea what might be happening? > Is there some debug logging we can enable to get better visibility to what's going on? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Fix Version/s: 10.4.0.AM3 (was: 10.4.0.AM2) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Nick Boldt > Labels: upstream > Fix For: 10.4.0.AM3 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24111: -------------------------------- Sprint: devex #130 April 2017 (was: devex #129 March 2017) > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.4.4.AM3 > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23308) Include Show in Terminal for CDK server adapter

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23308?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23308: -------------------------------- Sprint: devex #130 April 2017 (was: devex #129 March 2017) > Include Show in Terminal for CDK server adapter > ----------------------------------------------- > > Key: JBIDE-23308 > URL: https://issues.jboss.org/browse/JBIDE-23308 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.0.AM1 > > > As a follow up of JBIDE-21611 I noticed that Show in Console is now disabled for cdk server. That is correct as we've switched to the Terminal view for cdk. Would it be possible at all to add Terminal to the show in menu? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Fix Version/s: 4.4.4.AM3 (was: 4.4.4.AM2) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.4.AM3 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-4181. ------------------------------- Fix Version/s: 10.4.0.AM2 (was: 10.x) Resolution: Won't Fix > 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)

9 years

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