October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15794) Cordova Configuration Editor should be default editor for Cordova project config.xml file

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15794: ----------------------------------- Summary: Cordova Configuration Editor should be default editor for Cordova project config.xml file Key: JBIDE-15794 URL: https://issues.jboss.org/browse/JBIDE-15794 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Reporter: Vlado Pakan Fix For: 4.1.1.CR1 When Android tooling is installed in Eclipse default editor for Cordova project config.xml file is Android Common XML Editor. Would be nice to have Cordova Configuration Editor as default editor for this file. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15759) CLONE - new application wizard: switches from new to existing application when I change the domain

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15759?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15759: --------------------------------------- I could not reproduce the initial problem (the wizard was still in the "new application" mode after I switched the domain), but the patch fixes the missing error report since there's already an application with the same name in the second domain. So, +1 for the patch because the wizard now reports the error. > CLONE - new application wizard: switches from new to existing application when I change the domain > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-15759 > URL: https://issues.jboss.org/browse/JBIDE-15759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: respin-a > Fix For: 4.1.1.Beta1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15793) Cordova Plugin multiselection is not working

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15793: ----------------------------------- Summary: Cordova Plugin multiselection is not working Key: JBIDE-15793 URL: https://issues.jboss.org/browse/JBIDE-15793 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Reporter: Vlado Pakan Fix For: 4.1.1.CR1 1. Create new Hybrid Mobile project 2. Open config.xml file via Cordova Configuration Editor 3. Choose Add.. to add features, select more than one feature and click Finish ERROR: Only first selected feature is added to project and to config.xml file -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15792) JPP 6.1 project does not contain JBoss Portlet Libraries

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-15792: --------------------------------------- Summary: JPP 6.1 project does not contain JBoss Portlet Libraries Key: JBIDE-15792 URL: https://issues.jboss.org/browse/JBIDE-15792 Project: Tools (JBoss Tools) Issue Type: Bug Components: portal-gatein Affects Versions: 4.1.1.Beta1 Reporter: Radoslav Rábara Priority: Critical Fix For: 4.1.1.Beta1 Portal project with target runtime JPP 6.1.Final does not contain file "JBoss Portlet Libraries", so Java Portlet contains errors. However, if you create portal project with JPP 6.1.Beta then the file exists and no error is present. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15791) Run As toolbar button has wrong Tooltip once CordovaSim is closed

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15791: ----------------------------------- Summary: Run As toolbar button has wrong Tooltip once CordovaSim is closed Key: JBIDE-15791 URL: https://issues.jboss.org/browse/JBIDE-15791 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Reporter: Vlado Pakan Priority: Minor Fix For: 4.1.1.CR1 1. Create Hybrid Mobile project and run it in CordovaSim 2. Close CordovaSim ERROR: Run toolbar has tooltip Run <cordova project> (already running) even when CordovaSim is not running anymore -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15790) Adding backbutton listener disables backbutton functionality for all pages

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15790: ----------------------------------- Summary: Adding backbutton listener disables backbutton functionality for all pages Key: JBIDE-15790 URL: https://issues.jboss.org/browse/JBIDE-15790 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Reporter: Vlado Pakan Fix For: 4.1.1.CR1 1. Create new Hybrid Mobile Project 2. Add HTML page defining backbutton listener and link this page from index.html {noformat} <!DOCTYPE html> <html> <head> <title>Back Button Example</title> <script type="text/javascript" charset="utf-8" src="cordova.js"></script> <script type="text/javascript" charset="utf-8"> // Wait for device API libraries to load // function onLoad() { document.addEventListener("deviceready", onDeviceReady, false); } // device APIs are available // function onDeviceReady() { // Register the event listener document.addEventListener("backbutton", onBackKeyDown, false); } // Handle the back button // function onBackKeyDown() { alert('backbutton event fired'); } </script> </head> <body onload="onLoad()"> </body> </html> {noformat} 3. Add another HTML page and link it from index.html 4. Run project in CordovaSim 5. Navigate to page without backbutton listener and choose button Back ASSERT: Button back works index.html page is displayed 6. Navigate to page with buttonback listener 7. Choose button Back ASSERT: Alert box is displayed and no navigation to index.html happened 8. Open index.html page using address bar of CordovaSim 9. Navigate to page without backbutton listener and choose button Back ERROR: Nothing happened -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15612) install-grinder gets stuck after installing JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15612?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15612: ---------------------------------------- Actually, SWTBot timeout is configured to 15 minutes and the error in log appears 15 minutes after starting installation from Central. Then the confirm Exit dialog shows up and gets stucked (because the Test Thread has finished there), and waits for the job timeout, which is 840 minutes. I'll have a look at having the workbench actually close on test failure instead of getting the exit pop-up, but it's not the source of the error. The cause is that installation from Central takes more than 15 minutes, which seems a bit too long. Does installation from Central contact other p2 sites? > install-grinder gets stuck after installing JBDS > ------------------------------------------------ > > Key: JBIDE-15612 > URL: https://issues.jboss.org/browse/JBIDE-15612 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.1.1.Beta1, 4.1.1.CR1 > > Attachments: install-grinder-gets-stuck.png > > > Seems that the prompt at the end of the installation of JBDS is not being caught and clicked by the install grinder, so the eclipse instance stays open forever (until the job times out). > Steps to reproduce locally: > {code} > # as root, install these if not already installed > yum install tigervnc.x86_64 tigervnc-server.x86_64 vinagre -y > exit > # in a terminal, run this: > vncserver > # then launch vinagre to connect to the VNC session: > vinagre localhost:1 > # within the VNC session, run this: > git clone https://github.com/jbosstools/jbosstools-install-grinder/ > cd jbosstools-install-grinder > mvn org.apache.maven.plugins:maven-dependency-plugin:2.7:unpack \ > -Dartifact=org.jboss.tools.installation-tests:scripts:4.1.0.Beta1-SNAPSHOT:zip:delivery > cd scripts/target/scripts-*-delivery/ > SCRIPTDIR=`pwd` > WORKSPACE=/tmp/jbtcentraltarget-verify > rm -fr ${WORKSPACE}; mkdir -p ${WORKSPACE}; cd ${WORKSPACE} > # must be lowercase kepler > eclipseBundleVersion=kepler.R > # or > eclipseBundleVersion=kepler.SR1 > # path to where you store eclipse tar.gz files > eclipseCacheDirectory=${HOME}/tmp/Eclipse_Bundles > groovy ${SCRIPTDIR}/getAndInstallEclipse.groovy \ > eclipseCacheDirectory=${eclipseCacheDirectory} \ > eclipseBundleVersion=${eclipseBundleVersion} > INSTALL_PLAN="http://download.jboss.org/jbosstools/discovery/nightly/core/trunk/;http:/..." > # or > INSTALL_PLAN="http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/core/trunk/;http:..." > groovy ${SCRIPTDIR}/testInstall.groovy ${WORKSPACE}/eclipse/ $INSTALL_PLAN > {code} > Here's a screenshot: > !install-grinder-gets-stuck.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15787) Wildfly Server Adapter does not move to "started" state

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15787?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15787: --------------------------------------- Using default configuration for server adapter: - Startup Poller: Wildfly Manager Service - Shutdown Poller: Process Terminated Server ports: 0 / 8080 / 9990 Please, let me know if you need more information to reproduce the bug. > Wildfly Server Adapter does not move to "started" state > ------------------------------------------------------- > > Key: JBIDE-15787 > URL: https://issues.jboss.org/browse/JBIDE-15787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Reporter: Xavier Coulon > Attachments: Screen Shot 2013-10-25 at 10.56.42 AM.png, Screen Shot 2013-10-25 at 11.04.08 AM.png, Screen Shot 2013-10-25 at 11.04.22 AM.png, Screen Shot 2013-10-25 at 11.04.30 AM.png > > > Running on MacOSX. > Server is Wildfly 8.0.0.Beta1 > I created a server adapter, deployed a sample web application and when I start the server, I can see in the logs that the server started and deployed my application, but the server adapter seems blocked, waiting for server startup (see status bar on screenshot). > After a few minutes of waiting, the server adapter fails and stops the Wildfly server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15787) Wildfly Server Adapter does not move to "started" state

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15787?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15787: ---------------------------------- Attachment: Screen Shot 2013-10-25 at 11.04.08 AM.png Screen Shot 2013-10-25 at 11.04.22 AM.png Screen Shot 2013-10-25 at 11.04.30 AM.png Screen Shot 2013-10-25 at 10.56.42 AM.png Screenshots showing the 3 errors that occur when the Server Adapter thinks it failed to start the server (after a few minutes of waiting), and a screenshot showing the console output in which we can see that the Wildfly server actually started and the Server Adapter is still waiting. > Wildfly Server Adapter does not move to "started" state > ------------------------------------------------------- > > Key: JBIDE-15787 > URL: https://issues.jboss.org/browse/JBIDE-15787 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Reporter: Xavier Coulon > Attachments: Screen Shot 2013-10-25 at 10.56.42 AM.png, Screen Shot 2013-10-25 at 11.04.08 AM.png, Screen Shot 2013-10-25 at 11.04.22 AM.png, Screen Shot 2013-10-25 at 11.04.30 AM.png > > > Running on MacOSX. > Server is Wildfly 8.0.0.Beta1 > I created a server adapter, deployed a sample web application and when I start the server, I can see in the logs that the server started and deployed my application, but the server adapter seems blocked, waiting for server startup (see status bar on screenshot). > After a few minutes of waiting, the server adapter fails and stops the Wildfly server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15788: -------------------------------- Description: If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) - assert no EAP/AS7 are installed - create a new html5 project from central - click download and install for the server requirement - enter a non-existing location for the install folder !install_folder_must_exist.png! was: If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) - assert no EAP/AS7 are installed - create a new html5 project from central - click download and install for the server requirement - enter a non-existing location for the install folder > Download runtime wizard shouldn't complain if install folder doesn't exist > -------------------------------------------------------------------------- > > Key: JBIDE-15788 > URL: https://issues.jboss.org/browse/JBIDE-15788 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.1.Alpha2 > Reporter: Fred Bricon > Fix For: 4.1.1.CR1 > > Attachments: install_folder_must_exist.png > > > If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary) > - assert no EAP/AS7 are installed > - create a new html5 project from central > - click download and install for the server requirement > - enter a non-existing location for the install folder > !install_folder_must_exist.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, 6 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 October 2013