June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1120) Update QE tests for Oxygen

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1120?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1120: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/913 > Update QE tests for Oxygen > -------------------------- > > Key: JBTIS-1120 > URL: https://issues.jboss.org/browse/JBTIS-1120 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.3.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.5.0.AM1-TP > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24551) reactivate Sonarcloud.io updates for jbosstools-server

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-24551: --------------------------------------- Summary: reactivate Sonarcloud.io updates for jbosstools-server Key: JBIDE-24551 URL: https://issues.jboss.org/browse/JBIDE-24551 Project: Tools (JBoss Tools) Issue Type: Task Components: build, server Reporter: Aurélien Pupier last update was the 21 February !image-2017-06-08-11-44-59-190.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24291: ----------------------------------------- when I connect, expand some nodes, call refresh, collapse them then disconnect then reconnect, all the previously expanded node are loaded with a progress monitor which is not showing progress and stay blocked at 0% [^JMXLoad.mp4] > Improve initial loading of JMX Connection tree > ---------------------------------------------- > > Key: JBIDE-24291 > URL: https://issues.jboss.org/browse/JBIDE-24291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) > It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. > For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-24291: ------------------------------------ Attachment: JMXLoad.mp4 > Improve initial loading of JMX Connection tree > ---------------------------------------------- > > Key: JBIDE-24291 > URL: https://issues.jboss.org/browse/JBIDE-24291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: JMXLoad.mp4 > > > JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) > It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. > For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24535) itests are not run for server in Jenkins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24535: ------------------------------------- [~nickboldt] where is this new itests job? I haven't ever seen it or received an email of it failing. > itests are not run for server in Jenkins > ---------------------------------------- > > Key: JBIDE-24535 > URL: https://issues.jboss.org/browse/JBIDE-24535 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > I wanted to verify JBIDE-24483 which added itests for incremental deployment via management. But it turns out none of the itests are run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Shouldn't they be run? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24538) Wildfly 9 and above need remote+http protocol for jmx

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24538?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24538: ------------------------------------- Added a second commit. First was incomplete and I'm a dummy. > Wildfly 9 and above need remote+http protocol for jmx > ----------------------------------------------------- > > Key: JBIDE-24538 > URL: https://issues.jboss.org/browse/JBIDE-24538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > When connecting to a wf9 / wf10 / wf11 or associated eap's via jmx, console spits out the following: > {code} > Jun 05, 2017 4:16:34 PM org.jboss.remotingjmx.Util warnDeprecated > WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24547: ------------------------------------ If you're asking me, then my clarification is this: * If you want to enable a maven setting for a given folder-of-tests, then set that property in the root pom for that folder, eg., for AS' ITests, use https://github.com/jbosstools/jbosstools-server/pull/516 * If you want anything else, please ask for something else. > Refactor ITests settings in parent pom > -------------------------------------- > > Key: JBIDE-24547 > URL: https://issues.jboss.org/browse/JBIDE-24547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ). > The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24547 at 6/7/17 9:27 PM: ------------------------------------------------------------ If you're asking me, then my clarification is this: * If you want to enable a maven setting for a given folder-of-tests, then you should define that setting in the root pom for that folder, eg., for AS' ITests, use https://github.com/jbosstools/jbosstools-server/pull/516 * If you want anything else, please ask for something else. was (Author: nickboldt): If you're asking me, then my clarification is this: * If you want to enable a maven setting for a given folder-of-tests, then set that property in the root pom for that folder, eg., for AS' ITests, use https://github.com/jbosstools/jbosstools-server/pull/516 * If you want anything else, please ask for something else. > Refactor ITests settings in parent pom > -------------------------------------- > > Key: JBIDE-24547 > URL: https://issues.jboss.org/browse/JBIDE-24547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ). > The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24547: ------------------------------------- Can you clarify what you mean by unit tests vs integration tests? I would like to make sure you are not assuming all UI / reddeer tests are integration tests. I have a few plugins that are UI tests but are NOT integration tests. They are simple reddeer UI tests. You should not assume this fits cleanly into unit vs integration at all. > Refactor ITests settings in parent pom > -------------------------------------- > > Key: JBIDE-24547 > URL: https://issues.jboss.org/browse/JBIDE-24547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ). > The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24541) Exception in LocalFilesystemController.deleteResource

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24541?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24541: -------------------------------- Fix Version/s: 4.5.0.AM1 > Exception in LocalFilesystemController.deleteResource > ----------------------------------------------------- > > Key: JBIDE-24541 > URL: https://issues.jboss.org/browse/JBIDE-24541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Automated Error Reporting Bot > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > > The following problem was reported via the automated error reporting: > Message: Unable to delete module Module[mee-web,org.eclipse.jst.jee.server:mee-web] > java.lang.Exception: Could not delete /opt/keycloak-2.2.1.Final/standalone/deployments/mee-web-1.0-SNAPSHOT.war. May be locked by another process. > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.LocalFilesystemController.deleteResource(LocalFilesystemController.java:259) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.removeModule(StandardFileSystemPublishController.java:477) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.WildFlyFileSystemPublishController.removeModule(WildFlyFileSystemPublishController.java:36) > at org.jboss.tools.as.core.server.controllable.subsystems.internal.StandardFileSystemPublishController.publishModule(StandardFileSystemPublishController.java:338) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.publishModule(ControllableServerBehavior.java:143) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) > at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172) > at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > The reporter(s) left the following comment(s): > --- Anonymous wrote on 0a66: --- > Windows 10. Eclipse running as Administrator. > --- Anonymous wrote on 0d9a: --- > I have already deleted the folder manually myself as well as from Servers. This was what I did: Did Eclipse clean and build (not Wildfly 10 clean), and ran debug my other projects. > Not sure when you guys delete it; apparently it seems on the next run. I will not be checking this url, please email me on the results, thank you! > --- andremoriya wrote on ae18: --- > I Cleaned the wildfly server and run > Bundles: > | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.9.0.v20170322-0013 | > | org.eclipse.core.resources | 3.11.0.v20160503-1608 | 3.11.1.v20161107-2032 | > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.eclipse.debug.core | 3.10.100.v20160419-1720 | 3.10.100.v20160419-1720 | > | org.eclipse.debug.ui | 3.11.202.v20161114-0338 | 3.11.202.v20161114-0338 | > | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.2.v20170113-2113 | > | org.eclipse.ltk.core.refactoring | 3.7.0.v20160419-0705 | 3.7.0.v20160419-0705 | > | org.eclipse.ltk.ui.refactoring | 3.8.0.v20160518-1817 | 3.8.0.v20160518-1817 | > | org.eclipse.m2e.wtp.overlay | 1.3.2.20161026-1738 | 1.3.2.20161026-1738 | > | org.eclipse.wst.server.core | 1.8.0.v201601132253 | 1.9.0.v201610211907 | > | org.jboss.ide.eclipse.archives.webtools | 3.2.4.v20170329-2126 | 3.2.4.v20170329-2126 | > | org.jboss.ide.eclipse.as.ui | 3.2.2.v20161121-2100 | 3.2.4.v20170329-2126 | > | org.jboss.ide.eclipse.as.wtp.core | 3.2.2.v20161006-2008 | 3.2.4.v20170505-1406 | > Operating Systems: > | Linux | 3.2.0 | 4.10.10.fc25 | > | MacOSX | 10.10.5 | 10.12.5 | > | Windows | 6.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/580a0315e4b081752d6... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017