June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-757) Fuse: Add tests for cheat sheets

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-757?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-757: ------------------------------- Priority: Minor (was: Major) > Fuse: Add tests for cheat sheets > -------------------------------- > > Key: JBTIS-757 > URL: https://issues.jboss.org/browse/JBTIS-757 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Minor > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-757) Fuse: Add tests for cheat sheets

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-757: ---------------------------------- Summary: Fuse: Add tests for cheat sheets Key: JBTIS-757 URL: https://issues.jboss.org/browse/JBTIS-757 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-756) Fuse: Add tests for Invalid XML file handling

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-756: ---------------------------------- Summary: Fuse: Add tests for Invalid XML file handling Key: JBTIS-756 URL: https://issues.jboss.org/browse/JBTIS-756 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík There was several bugs reported which handled to data loss when an xml file modified by hand and if no data loss, at least it was messed up and user has no information to solve the issue. It will be nice to have UI tests about the following usecases: * Opening of an invalid XML file and switch between Design/Source/configuration editor tabs see https://issues.jboss.org/browse/FUSETOOLS-1608 for instance * Opening a valid Camel context file, go to Source and modify it to be invalid, switch to other tabs * add yours... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22536) Docker New and Noteworthy for 4.4.0.Final

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22536?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-22536. --------------------------------- New features added in doc. > Docker New and Noteworthy for 4.4.0.Final > ----------------------------------------- > > Key: JBIDE-22536 > URL: https://issues.jboss.org/browse/JBIDE-22536 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Final > > > If no news for 4.4.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.4.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "page-include-previous: false" attribute to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22597) Deploy docker image to openshift may finish without user being notified

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22597: ---------------------------------- Summary: Deploy docker image to openshift may finish without user being notified Key: JBIDE-22597 URL: https://issues.jboss.org/browse/JBIDE-22597 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff MAURY Fix For: 4.4.1.Alpha1 When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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: --------------------------------------- BTW, this happened in previous versions and was reported in JBIDE-20323 and JBIDE-20490 . I saw it again today, but that was when I was running EAP 6.4 in one instance of Eclipse and then tried to start WildFly 10 in another. I chose to mark it as started. And then it's not surprising that it couldn't connect to the running server - the libs are different. But yeah, Max is right - they're not really remote deployments, it's a local server. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3947: ------------------------------------- fixed 1.6.5 scenario, but in case 1.7.0 it wont be detected at all. > Some older versions of vagrant skip version validation > ------------------------------------------------------ > > Key: JBDS-3947 > URL: https://issues.jboss.org/browse/JBDS-3947 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.1.Alpha1 > > Attachments: vagrant.png > > > Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though. > !vagrant.png|thumbnail! > The issue might be connected to the fact that with these versions the command > {noformat}where vagrant{noformat} > in fact returns 2 files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3947: -------------------------------- Fix Version/s: 10.0.1.Alpha1 > Some older versions of vagrant skip version validation > ------------------------------------------------------ > > Key: JBDS-3947 > URL: https://issues.jboss.org/browse/JBDS-3947 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.0.1.Alpha1 > > Attachments: vagrant.png > > > Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though. > !vagrant.png|thumbnail! > The issue might be connected to the fact that with these versions the command > {noformat}where vagrant{noformat} > in fact returns 2 files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22272) NPE when using LaunchBar to run an app on WildFly

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22272?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22272. --------------------------------- Hmm, the other issue talked about null target. I don't think the target was null in this case. But anyway, it seems to be fixed - I tried it now and there are no NPEs. Verified in 4.4.0. Closing. > NPE when using LaunchBar to run an app on WildFly > ------------------------------------------------- > > Key: JBIDE-22272 > URL: https://issues.jboss.org/browse/JBIDE-22272 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Final > > > I tried to run jboss java ee web app from Central on WildFly 10 using launchbar. And it did work, but a NPE was thrown: > {code} > Plug-in: org.eclipse.debug.core > An exception occurred during launch change notification. > java.lang.NullPointerException > at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:84) > at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128) > at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964) > at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942) > at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424) > at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423) > at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433) > at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043) > at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-20915. ------------------------------- Closing as done. > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Labels: documentation > Fix For: 4.4.0.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016