July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4469) Some servers are only added to runtime detection when fuse tooling is installed/not installed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4469?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4469: -------------------------------- Story Points: 3 > Some servers are only added to runtime detection when fuse tooling is installed/not installed > --------------------------------------------------------------------------------------------- > > Key: JBDS-4469 > URL: https://issues.jboss.org/browse/JBDS-4469 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > > Namely: > - EAP is only added if fuse tooling is not installed > - Fuse runtimes are only added if fuse tooling is installed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

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: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017, devex #132 May 2017, devex #135 July 2017 (was: devex #127 February 2017, devex #128 February 2017, devex #132 May 2017) > 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.5.x > > > 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)

8 years, 8 months

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: -------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM2) > 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.5.x > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24652) update target platform & Central to Oxygen.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24652: ------------------------------- Sprint: devex #135 July 2017 (was: devex #134 Jun 2017) > update target platform & Central to Oxygen.0+ > --------------------------------------------- > > Key: JBIDE-24652 > URL: https://issues.jboss.org/browse/JBIDE-24652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Issue to track changes to target platform after AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4470) Load configuration from remote location to allow updates without releasing installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4470: ----------------------------------- Summary: Load configuration from remote location to allow updates without releasing installer Key: JBDS-4470 URL: https://issues.jboss.org/browse/JBDS-4470 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Affects Versions: 11.0.0.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 11.0.0.GA -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24648) update target platform to include jetty 9.4.6 (CVE issue)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24648?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24648: ------------------------------- Sprint: devex #135 July 2017 (was: devex #134 Jun 2017) > update target platform to include jetty 9.4.6 (CVE issue) > --------------------------------------------------------- > > Key: JBIDE-24648 > URL: https://issues.jboss.org/browse/JBIDE-24648 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Fedora and RHEL have updated to Jetty 9.4.6 due to this CVE: > * https://bugzilla.redhat.com/show_bug.cgi?id=1464158 > Currently, JBT/devstudio target platform includes Jetty 9.4.5, as that's what was in Oxygen.0.RC4. > But we could move to a newer version if we want to have the same version in linux and in windows/OSX versions of JBT/devstudio. > Affected manifest files (which require jetty bundles from *[9.4.0,9.5.0)*) > * [1] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/META-INF/MANIFEST.MF > * [2] ./jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim/META-INF/MANIFEST.MF > * [3] ./jbosstools-aerogear/cordovasim/tests/org.jboss.tools.cordovasim.eclipse.test/META-INF/MANIFEST.MF > * [4] ./jbosstools-base/foundation/tests/org.jboss.tools.foundation.core.test/META-INF/MANIFEST.MF > * [5] ./jbosstools-browsersim/plugins/org.jboss.tools.browsersim.ui/META-INF/MANIFEST.MF > * [6] ./jbosstools-central/central/tests/org.jboss.tools.central.test/META-INF/MANIFEST.MF > * [7] ./jbosstools-livereload/plugins/org.jboss.tools.livereload.core/META-INF/MANIFEST.MF > * [8] ./jbosstools-livereload/tests/org.jboss.tools.livereload.test/META-INF/MANIFEST.MF > * [9] ./jbosstools-server/jmx/tests/org.jboss.tools.jmx.jolokia.test/META-INF/MANIFEST.MF -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24561) replace TextFinderPublisher w/ new customizable log-parser plugin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24561: ------------------------------- Sprint: devex #135 July 2017 (was: devex #134 Jun 2017) > replace TextFinderPublisher w/ new customizable log-parser plugin > ----------------------------------------------------------------- > > Key: JBIDE-24561 > URL: https://issues.jboss.org/browse/JBIDE-24561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Description setter plugin seems to take 80 mins to parse the console log. > So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken! > {code} > 10:05:56 Terminating xvnc. > 10:05:56 $ /usr/bin/vncserver -kill :33 > 10:05:57 Killing Xvnc process ID 9997 > 10:05:59 Archiving artifacts > 10:05:59 Checking console output > 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com > {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > 10:04:53 Terminating xvnc. > 10:04:53 $ /usr/bin/vncserver -kill :35 > 10:04:54 Killing Xvnc process ID 9993 > 10:04:56 Archiving artifacts > 10:04:57 Checking console output > 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT' > 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24572) use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24572?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24572: ------------------------------- Sprint: devex #135 July 2017 (was: devex #134 Jun 2017) > use M2_HOME=${COMMON_TOOLS}/apache-maven-3.3.9/ instead of hard coding the path to /qa/tools/opt > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24572 > URL: https://issues.jboss.org/browse/JBIDE-24572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Jobs should use global slave-specific variable COMMON_TOOLS to define path to maven binary, eg., this change: > https://dev-platform-jenkins-rhel7.rhev-ci-vms.eng.rdu2.redhat.com/job/jb... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4160) Closing terminal opened during Container Development Environment start terminates vagrant process

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4160?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4160: ------------------------------ Fix Version/s: 11.x (was: 11.0.0.AM2) > Closing terminal opened during Container Development Environment start terminates vagrant process > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4160 > URL: https://issues.jboss.org/browse/JBDS-4160 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 10.1.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Minor > Fix For: 11.x > > > Closing terminal with running vagrant up command terminates startup process without any warning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20108: -------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM2) > Cannot connect to remote server in JMX Navigator - Authentication fails > ----------------------------------------------------------------------- > > Key: JBIDE-20108 > URL: https://issues.jboss.org/browse/JBIDE-20108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > When I try to connect to a remote server via JMX Navigator, it fails on authentication: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854 > !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > ... 7 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854 > !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > !STACK 0 > javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work. > Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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