April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3850: ----------------------------------- Summary: Test code coverage console report for platform installer unit tests Key: JBDS-3850 URL: https://issues.jboss.org/browse/JBDS-3850 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Affects Versions: 10.0.0.Alpha1 Reporter: Denis Golovin Assignee: Pavol Pitonak Fix For: 10.0.0.Alpha1 Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20362: --------------------------------------- [~rob.stryker], I gave this another go now and I have an update: I noticed that when I download a runtime via the New Server wizard, the unzipping is fast. But if I go via Preferences > Runtime Detection > Download, it is slow. So maybe you could check what's different between the two? The progress window is slightly different and I can see that when it's slow, each directory is printed twice - once above the progress bar and once below, but I doubt this would make such a huge difference, so there must be more that's different. > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3750) Include Virtual Box 5.0.16 (instead of 5.0.8) in the bundled installer

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3750?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3750: ------------------------------------- FYI ORG-3019 is resolved now. > Include Virtual Box 5.0.16 (instead of 5.0.8) in the bundled installer > ---------------------------------------------------------------------- > > Key: JBDS-3750 > URL: https://issues.jboss.org/browse/JBDS-3750 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.0.0.Alpha1 > > > Latest version of VB available [1] is 5.0.16. > We should update the installer to include the latest, rather than 5.0.8. > [1] https://www.virtualbox.org/wiki/Downloads -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-19854. ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.4.x) Resolution: Cannot Reproduce Bug Cannot replicate. Please let us know if you still see this. In that case we would need some way to reproduce. > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Assignee: Martin Malina > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Fix For: 4.3.1.Final > > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19854) When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19854?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19854: --------------------------------------- [~rob.stryker], I tried starting WildFly 8.1 in debug mode in JBDS 9.1.0.GA on Windows 10 and it starts up fine for me. > When Wildfly starts in debug mode occurs ClassNotFoundException with org.jboss.modules.Main > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19854 > URL: https://issues.jboss.org/browse/JBIDE-19854 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java Version 1.7.0_75; > Reporter: Giancarlo giulian > Assignee: Martin Malina > Labels: classnotfound, debug, debugging, jboss, main, wildfly > Fix For: 4.4.x > > Attachments: image2.png, image3.png, imagem1.png > > > This problem has recently begun, before that is it working in debug mode. Errors log are not created and doesn't appear in console output using Eclipse Luna. > Program Arguments: > {quote} > -mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\wildfly-8.1\standalone > {quote} > VM Arguments: > {quote} > "-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log" "-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties" "-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost > {quote} > Images: > https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png > https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19453: --------------------------------------- And I'm still seeing this in JBDS 9.1.0.GA ;) > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Labels: help_wanted > Fix For: LATER > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png, server-editor-linux.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21743) no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21743?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21743: --------------------------------------- The only warning I get after importing this is: No connection specified for project. No database-specific validation will be performed. > no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21743 > URL: https://issues.jboss.org/browse/JBIDE-21743 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Importing "spring-kitchensink-basic" EAP7 quickstart raises an error: > {noformat}Description Resource Path Location Type > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-basic/src/main/webapp/WEB-INF line 26 XML Problem > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3848: ------------------------------------- I cannot replicate this. I installed JBDS 9.1.0.GA standalone on Windows 10 and I have all the types. But I have an idea, [~ldimaggio], have you tried expanding the window size? Maybe it's just that for some reason the window showed up too small, so there's no room for the list of server types? > Server adapter types not displayed on Windows10 for JBDS 9.1.0 > -------------------------------------------------------------- > > Key: JBDS-3848 > URL: https://issues.jboss.org/browse/JBDS-3848 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: server, upstream > Affects Versions: 9.1.0.GA > Environment: Version: 9.1.0.GA > Build id: GA-v20160414-0124-B497 > Build date: 20160414-0124 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Priority: Blocker > Attachments: CDK_RHEL.png, CDK_Win10.png > > > See attached screenshots - after installing 9.1.0, server adapters are seen on RHEL, not on Windows10. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20753: --------------------------------------- [~rob.stryker], yes, I can still replicate this in JBDS 9.1.0.GA on Mac and Windows (I don't have Linux near me). > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: regression > Fix For: 4.4.0.Alpha1 > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20798) log filling up with "unable to retrieve a list of remote deployments"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20798?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20798: --------------------------------------- [~rob.stryker], no, I cannot replicate this either. I do recall seeing this error not too long ago, but I don't see it now. Would be good if Max had exact steps to reproduce. > log filling up with "unable to retrieve a list of remote deployments" > --------------------------------------------------------------------- > > Key: JBIDE-20798 > URL: https://issues.jboss.org/browse/JBIDE-20798 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > Attachments: Java_EE_-_JBoss_EAP_6_4_-_Eclipse_-__Users_max_Documents_workspace-deploy-demo.png > > > when starting/stopping EAP 6.4 server I 'm getting my logs filled with: > {code} > Unable to retrieve a list of remote deployment scanners > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361) > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.management.core.service.DelegatingManagerService.execute(DelegatingManagerService.java:132) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:236) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:234) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:122) > at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDefaultDeploymentScanner(AS7DeploymentScannerUtility.java:212) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadDefaultScannerFromServer(LocalJBoss7DeploymentScannerAdditions.java:148) > at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersAdded(LocalJBoss7DeploymentScannerAdditions.java:58) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.updateDeploymentScanners(AbstractDeploymentScannerAdditions.java:61) > at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions$1.run(AbstractDeploymentScannerAdditions.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-resource" for [ > {"subsystem" => "deployment-scanner"}, > {"scanner" => "*"} > ]. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available". > at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352) > ... 15 more > {code} > since these are done during startup and it is possible to see in the error then I would expect we did not log this by default for this case. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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