February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16549) Install grinder fails to close the welcome screen -- WidgeNotFoundException: There is no active view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16549?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16549: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Install grinder fails to close the welcome screen -- WidgeNotFoundException: There is no active view > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-16549 > URL: https://issues.jboss.org/browse/JBIDE-16549 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.2.0.Alpha2 > Reporter: Pavol Srna > Fix For: 4.2.0.Beta1 > > > I tried with the latest JBT 4.2.0.Alpha2a build. > StackTrace: > -------------------- > There is no active view > org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: There is no active view > at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.activeView(SWTWorkbenchBot.java:200) > at org.jboss.tools.tests.installation.InstallFromCentralTest.setUp(InstallFromCentralTest.java:52) > at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:54) > at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350) > at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208) > at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:116) > at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72) > at java.lang.Thread.run(Thread.java:744) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16538) Enhance bpel publisher to work over rse, also use new api

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16538?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16538: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Enhance bpel publisher to work over rse, also use new api > --------------------------------------------------------- > > Key: JBIDE-16538 > URL: https://issues.jboss.org/browse/JBIDE-16538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel, server > Affects Versions: 4.2.0.Alpha2 > Reporter: Rob Stryker > Assignee: Robert (Bob) Brodt > Fix For: 4.2.0.Beta1 > > > The BPEL publisher is currently using legacy api's that will be removed in astools 3.0. Aside from that, it does not work over rse connections to remote servers. > A patch will be coming to assist in your migration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16625) Long left panel covers footer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16625?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16625: ---------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Long left panel covers footer > ----------------------------- > > Key: JBIDE-16625 > URL: https://issues.jboss.org/browse/JBIDE-16625 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: website > Environment: Chrome on Linux (Fedora 18, 64b) > Reporter: Radim Hopp > Fix For: 4.2.0.Beta1 > > Attachments: website-fixed.png, website.png > > > When the left panel is longer than some value and page is scrolled to the bottom, it covers part of footer making it unable to access few links from footer without scrolling back up: > !website.png! > Solution could be to "stuck" left panel on bottom of the page and scroll it up (like it is doing on the top of the page) so it would look like this: > !website-fixed.png! > And one more little thing (i don't think it deserves its own jira): The thin line just above the footer is on top of left panel and imo should be under. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16640) Avoid bumping dependencies versions unless it is required

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-16640: ------------------------------------- Summary: Avoid bumping dependencies versions unless it is required Key: JBIDE-16640 URL: https://issues.jboss.org/browse/JBIDE-16640 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.2.0.Alpha2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.Beta1 Problem occurred when trying to install LiveReload 1.2.0.Alpha2 on Kepler: {code} Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) Software currently installed: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) Only one of the following can be installed at once: Browser Support 3.4.100.v20130527-1656 (org.eclipse.ui.browser 3.4.100.v20130527-1656) Browser Support 3.4.200.v20131003-1453 (org.eclipse.ui.browser 3.4.200.v20131003-1453) Cannot satisfy dependency: From: Eclipse Standard/SDK 2.0.1.20130919-0803 (epp.package.standard 2.0.1.20130919-0803) To: org.eclipse.epp.package.standard.feature.feature.group [2.0.1.20130919-0803] Cannot satisfy dependency: From: Eclipse Standard/SDK Feature 2.0.1.20130919-0803 (org.eclipse.epp.package.standard.feature.feature.group 2.0.1.20130919-0803) To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000] Cannot satisfy dependency: From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000) To: org.eclipse.ui.browser [3.4.100.v20130527-1656] Cannot satisfy dependency: From: JBoss Tools LiveReload Core 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.core 1.2.0.Alpha2-v20140207-2102-B6) To: bundle org.eclipse.ui.browser 3.4.200 Cannot satisfy dependency: From: JBoss Tools LiveReload 1.2.0.Alpha2-v20140207-2102-B6 (org.jboss.tools.livereload.feature.feature.group 1.2.0.Alpha2-v20140207-2102-B6) To: org.jboss.tools.livereload.core [1.2.0.Alpha2-v20140207-2102-B6] {code} AFAIR, there was no real need to bump org.eclipse.ui.browser from 3.4.100 to 3.4.200. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16588: ------------------------------------- To add a bit more info, the recent patch I just committed fixed a situation where we didn't get to save the pid so we couldn't force terminate via kill later. I believe this is fixed, but I'd like you to verify since my remote server is crap and I test lately via rse using local host. > Remote EAP 6.2 fails to stop > ---------------------------- > > Key: JBIDE-16588 > URL: https://issues.jboss.org/browse/JBIDE-16588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2a B70 > EAP 6.2.0.GA > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: remote-server-stop-error.png > > > When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239 > !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop. > {code} > Very informative ;) > !remote-server-stop-error.png! > The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16588: ------------------------------------- Well with the latest patches in master, exposing management port is the default for all as7 or later when in rse mode... I know for as>7 we also used to terminate the remote process using a kill command, and I think I solved a bug today with rse host shells... see JBIDE-16634 I suggest you try this again once there's a new build on master [~mmalina]. It may very well be fixed :) I'll give it another run through too. > Remote EAP 6.2 fails to stop > ---------------------------- > > Key: JBIDE-16588 > URL: https://issues.jboss.org/browse/JBIDE-16588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2a B70 > EAP 6.2.0.GA > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: remote-server-stop-error.png > > > When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239 > !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop. > {code} > Very informative ;) > !remote-server-stop-error.png! > The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16588: --------------------------------------- I'm not 100% sure, but I think this worked in the past - even if management port was not set up, the tools would shutdown the server using the shutdown script. If that's not possible anymore and the only way to make EAP6/AS7/WF work remotely is by setting up management, then this would require some changes in the UI - it would have to be the default and only option - why give users an option that will never work. > Remote EAP 6.2 fails to stop > ---------------------------- > > Key: JBIDE-16588 > URL: https://issues.jboss.org/browse/JBIDE-16588 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2a B70 > EAP 6.2.0.GA > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: remote-server-stop-error.png > > > When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error: > {code} > !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239 > !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop. > {code} > Very informative ;) > !remote-server-stop-error.png! > The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15502) Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15502?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15502. --------------------------------- Verified in JBDS 8.0.0.Alpha2b B71 > Internal browser is using wrong URL if launched for already deployed ear-app via Servers tab > -------------------------------------------------------------------------------------------- > > Key: JBIDE-15502 > URL: https://issues.jboss.org/browse/JBIDE-15502 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Tomas Repel > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > I am using JBDS 7.0.0.GA with Integration Stack, EAP 6.1.0 is configured in Servers tab. When importing JDF example ejb-in-ear [1], then right-click on jboss-ejb-in-ear-ear -> Run As -> Run on Server, the example is deployed and the internal browser window is opened automatically using following URL: http://localhost:8080/jboss-ejb-in-ear/greeter.jsf (this is correct behavior). > If you go to Servers tab, expand the EAP 6.1 Server, right-click on deployed jboss-ejb-in-ear-ear, use Show in menu item and then click Web Browser, the internal browser is opened with wrong URL (http://localhost:8080/jboss-ejb-in-ear-web/). > It seems the configuration in application.xml file is ignored for some reason. > [1] http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/ejb-in-ear/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15915) Large-scale refactor to split major functionality into clear systems with public API

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15915?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15915. --------------------------------- Closing. > Large-scale refactor to split major functionality into clear systems with public API > ------------------------------------------------------------------------------------ > > Key: JBIDE-15915 > URL: https://issues.jboss.org/browse/JBIDE-15915 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > ASTools currently suffers from tight coupling, mixing of API and non-API classes, an API that is not clear, a very long unit test run, and other symptoms which stem from the above problems. Several newer use-cases are impossible to solve without making the problem worse. > To solve these issues, ASTools needs to have its major functionality split up and separated. The API for each system needs to be clearly apparent and easy to use, from both core, ui, and other consumers. In general, if UI classes are not using the API and are reaching in to internal classes, then the API is insufficient and needs to be cleaned up. > This large-scale refactor will focus first on the deploy-only server as an example and can eventually be (easily) extended to the other server types. > https://community.jboss.org/wiki/JBossTools-DelegatingServersViaSubsystems -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16349) Wizards for new Wildfly 8 server/runtime show "JBoss Application Server 8.0"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16349?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16349. --------------------------------- Verified in JBDS 8.0.0.Alpha1b B71 > Wizards for new Wildfly 8 server/runtime show "JBoss Application Server 8.0" > ---------------------------------------------------------------------------- > > Key: JBIDE-16349 > URL: https://issues.jboss.org/browse/JBIDE-16349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Final > Environment: Kepler SR1 + JBoss AS Tools 2.4.101.Final-v20131206-1843-B159 (installed from WTP's download runtime feature) > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > Attachments: wildfly-wizard.png > > > If you create a new Wildfly 8 runtime or a new server, the description in the wizard page says "JBoss Application Server 8.0" > !wildfly-wizard.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 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 February 2014