March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16661) need to have process launch console output for BrowserSim / CordovaSim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16661?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-16661: ------------------------------------- [~maxandersen], I have successfully implemented process launch console output (including callbacks). The only problem I have is the output coloring. Although we do have *!JavaScript LOG , !JavaScript Warn etc.* prefixes, it would be really nice to have messages colored. For now I have only two options: *red* - for js errors, and *black* for other messages. Is it something we can abide or console message coloring should be added (console.info -> blue; console.warn -> yellow)? AFAIK there is no OOTB solution. > need to have process launch console output for BrowserSim / CordovaSim > ---------------------------------------------------------------------- > > Key: JBIDE-16661 > URL: https://issues.jboss.org/browse/JBIDE-16661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Reporter: Konstantin Marmalyukov > Assignee: Ilya Buziuk > Fix For: 4.2.0.Beta2 > > Attachments: Screenshot 2014-02-27 16.23.47.png > > > If I understand everything correct from email thread [~maxandersen] wants to have something like in attached screenshot(standart console where error log and terminate button presents) for BrowserSim and CordovaSim launching. > My point that it could be done for CordovaSim because it's a launch tool, but not for BrowserSim because it's "just a browser". -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16939) OpenShift application creation should not lock the UI while waiting for DNS to propagate

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16939?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-16939: -------------------------------------------- As I mentioned in the original description, this occurs simply by completing the OpenShift New Application wizard. 1. In the "OpenShift" view, right click on your account. 2. Select "New" -> "Application" 3. Enter an application name and select the gear type (I used EAP6 and a small gear) 4. Click "Finish" OpenShift will now create the application and propagate the new DNS entry out to "the internet" - This can take quite some time, anywhere from 5 seconds to 5 minutes. The dialog remains open until this operation is finished. It is not possible to put this into the background. Additionally. As I just discovered while attempting to give exact steps. If you take too long to accept the RSA Fingerprint Dialog Box, the Git streaming operation times out and the application fails to import entirely. I highly doubt this is environment specific, but I use OSX 10.9.2 with Oracle Java 1.7_51 on a 64bit quad core intel i7 with hyper-threading and 16mb of memory. > OpenShift application creation should not lock the UI while waiting for DNS to propagate > ---------------------------------------------------------------------------------------- > > Key: JBIDE-16939 > URL: https://issues.jboss.org/browse/JBIDE-16939 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Lincoln Baxter III > > After completing the OpenShift -> New Application wizard, the UI locks while Eclipse waits for the OpenShift operation to complete. Many OpenShift operations (including application creation) can take quite a while, and it should be able to be moved to the background, allowing the user to continue working while waiting. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16955) Daily usage event reporting job (sleeping) stays in Progress View

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16955: ----------------------------------- Summary: Daily usage event reporting job (sleeping) stays in Progress View Key: JBIDE-16955 URL: https://issues.jboss.org/browse/JBIDE-16955 Project: Tools (JBoss Tools) Issue Type: Bug Components: usage Affects Versions: 4.2.0.Beta1 Reporter: Fred Bricon Assignee: Alexey Kazakov Priority: Minor Fix For: 4.2.0.Beta2 After restarting the workbench, "Daily usage event reporting job (sleeping)" stays in Progress View forever. !http://content.screencast.com/users/fbricon/folders/Jing/media/92f4cca0-5a94-45ac-b2c2-ce2d60c1aee3/daily-usage-reporting-job.png! I'm pretty sure it's gonna scare/annoy some users -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16953) when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16953?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16953: ------------------------------------ Fixed in master: https://github.com/jbosstools/jbosstools-build-ci/commit/c522b9cfb85b1d56... Spinning to verify: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=3147 http://download.jboss.org/jbosstools/builds/nightly/webtools/master/2014-... (empty) http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... (should no longer be empty) > when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16953 > URL: https://issues.jboss.org/browse/JBIDE-16953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > when skipRevisionCheck=false, publish.sh [1] thinks an empty GIT_REVISION file [2] means no changes since last build. Instead, it should see an empty file as "unknown status" and publish the new build. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > [2] http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/logs/G... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16953) when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16953?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-16953 at 3/31/14 11:12 AM: -------------------------------------------------------------- Fixed in master: https://github.com/jbosstools/jbosstools-build-ci/commit/c522b9cfb85b1d56... https://github.com/jbosstools/jbosstools-build-ci/commit/f54651ea88df2eee... Spinning to verify: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=3147 http://download.jboss.org/jbosstools/builds/nightly/webtools/master/2014-... (empty) http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... (should no longer be empty) was (Author: nickboldt): Fixed in master: https://github.com/jbosstools/jbosstools-build-ci/commit/c522b9cfb85b1d56... Spinning to verify: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... >=3147 http://download.jboss.org/jbosstools/builds/nightly/webtools/master/2014-... (empty) http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... (should no longer be empty) > when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16953 > URL: https://issues.jboss.org/browse/JBIDE-16953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > > when skipRevisionCheck=false, publish.sh [1] thinks an empty GIT_REVISION file [2] means no changes since last build. Instead, it should see an empty file as "unknown status" and publish the new build. > [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > [2] http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/logs/G... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16954) Command 'cd #' not implemented in Forge2

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-16954: ---------------------------------- Summary: Command 'cd #' not implemented in Forge2 Key: JBIDE-16954 URL: https://issues.jboss.org/browse/JBIDE-16954 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.0.Beta1 Reporter: Pavol Srna Fix For: 4.2.0.Beta2 I'm missing 'cd #' command in Forge2. Would it be possible to make the forge "cd" command aware of the eclipse workspace the same way as it is in Forge1? -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16953) when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16953: ---------------------------------- Summary: when skipRevisionCheck=false, publish.sh thinks an empty GIT_REVISION file means no changes since last build Key: JBIDE-16953 URL: https://issues.jboss.org/browse/JBIDE-16953 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.2.0.Beta1 when skipRevisionCheck=false, publish.sh [1] thinks an empty GIT_REVISION file [2] means no changes since last build. Instead, it should see an empty file as "unknown status" and publish the new build. [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... [2] http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/logs/G... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16952) Greater-than sign incorrectly considered an invalid character in HTML5 text

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-16952: ---------------------------------- Summary: Greater-than sign incorrectly considered an invalid character in HTML5 text Key: JBIDE-16952 URL: https://issues.jboss.org/browse/JBIDE-16952 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Environment: JBoss Tools version that is in JBDS 7.1.1.GA Reporter: Ron Šmeral Priority: Minor A HTML5 file like the following {code:html} <!DOCTYPE html> <html> <head><title>README</title></head> <body> <p>To run the tests, select Run As –> JUnit Test in the context menu.</p> </body> </html> {code} results in a warning of type _HTML Problem_ with the text _Invalid character used in text string_, marking the greater-than sign (">"). This warning is incorrect, since ">" is a valid character in HTML5 text elements as confirmed by the W3C validator. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16951) Update code that uses the OSJC ssh sessions to use the new ApplicationSSHSession class

by Corey Daley (JIRA)

Corey Daley created JBIDE-16951: ----------------------------------- Summary: Update code that uses the OSJC ssh sessions to use the new ApplicationSSHSession class Key: JBIDE-16951 URL: https://issues.jboss.org/browse/JBIDE-16951 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Reporter: Corey Daley Fix For: 4.2.0.Beta2 Need to update any code that referenced methods inside of IApplication that used an SSH session to use the new IApplicationSSHSession interface that only contains methods that use the ssh sessions. JIRA for the OSJC can be found here: https://issues.jboss.org/browse/OSJC-54 -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2992) Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-2992?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBDS-2992. ---------------------------- Fix Version/s: 7.1.x Resolution: Done I was able to reproduce this bug with JBDSIS 7.0.0.GA - this issue no longer exists with JBDSIS 7.0.1.CR2. Please retest using this update site URL: https://devstudio.jboss.com/updates/7.0-development/integration-stack/ > Generated CustomerWebServiceTest can not run on JBoss Dev Studio integration-stack > ---------------------------------------------------------------------------------- > > Key: JBDS-2992 > URL: https://issues.jboss.org/browse/JBDS-2992 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: integration > Environment: Both RHEL and Windows > Oracle JDK1.7.0_25 > JBDS7.1.1 > updated Fuse integration-stack > Reporter: Xiaohui Wu > Assignee: Paul Leacu > Fix For: 7.1.x > > > Added Fuse integration-stack to JBoss Dev Studio at: https://devstudio.jboss.com/updates/7.0/integration-stack/ > Following instructions here: > http://www.jboss.org/products/fuse > Created new project using camel-webservice archetype. Build it, and try to Run As -> Local Camel Context. You will see there is an erro indicated cannot find the file: > {code} > org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [META-INF/spring/camelContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [META-INF/spring/camelContext.xml] cannot be opened because it does not exist > at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341) > at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302) > at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174) > at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209) > {code} > in fact the generated fileName is CamelContext.xml, not camelContext.xml -- 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

11 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 March 2014