December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-15932: ------------------------------------- need this fixed in JBT 4.1.2 / JBDS 7.1.1 > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-15932: -------------------------------- Priority: Blocker (was: Critical) > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Priority: Blocker > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-15932: ------------------------------------- Firebug Lite in its current form is not a good solution: 1) it can not display console.log from deviceready 2) it "swallows" JS syntax errors 3) it auto-closes when using LiveReload > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-15932: -------------------------------- Priority: Critical (was: Major) > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15932) CordovaSim needs to display console logs

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15932?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-15932: ------------------------------------- What about JS syntax errors? Those are currently swallowed. > CordovaSim needs to display console logs > ---------------------------------------- > > Key: JBIDE-15932 > URL: https://issues.jboss.org/browse/JBIDE-15932 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.1.Beta1 > Reporter: Gorkem Ercan > Assignee: Konstantin Marmalyukov > Fix For: 4.2.0.Alpha2 > > > When a cordova application is launched the console.log calls are not displayed on Eclipse console (or anywhere else). CordovaSim needs a place to display the logs either within eclipse or on the Ripple console -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15185: ------------------------------------- I've added an upstream bugzilla enhancement request. https://bugs.eclipse.org/bugs/show_bug.cgi?id=424445 > add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory. > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15185 > URL: https://issues.jboss.org/browse/JBIDE-15185 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Fix For: 4.2.x > > > The current jbds version only allow users to specify an absolute path for "Home Directory" when creating JBoss Runtime Server. Is it possible to use a user defined variable here? -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-16280 at 12/18/13 7:47 PM: ----------------------------------------------------------------- FAQ should be updated then in wiki and mention this problem. It is probably good idea to mention this workaround right in VPE part error message when xulrunner plugin is found but SWT_GTK3 is not exported. was (Author: dgolovin): FAQ should be updated then in wiki and mention this problem. It probably good idea to mention this workaround right in VPE part error message. > VPE/XulRunner crashes workbench > ------------------------------- > > Key: JBIDE-16280 > URL: https://issues.jboss.org/browse/JBIDE-16280 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xulrunner > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Priority: Critical > Fix For: 4.2.0.Alpha2 > > Attachments: hs_err_pid20688.log, install-locally-built-vpe-from-4-sites.png > > > After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup. > JVM creates me a thread dump, that you can find attached. Here is the header: > {code} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584 > # > # JRE version: 7.0_25-b30 > # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2 > # > {code} > I'm running on Ubuntu 12.04. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-16280: --------------------------------------- FAQ should be updated then in wiki and mention this problem. It probably good idea to mention this workaround right in VPE part error message. > VPE/XulRunner crashes workbench > ------------------------------- > > Key: JBIDE-16280 > URL: https://issues.jboss.org/browse/JBIDE-16280 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xulrunner > Affects Versions: 4.2.0.Alpha1 > Reporter: Mickael Istria > Priority: Critical > Fix For: 4.2.0.Alpha2 > > Attachments: hs_err_pid20688.log, install-locally-built-vpe-from-4-sites.png > > > After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup. > JVM creates me a thread dump, that you can find attached. Here is the header: > {code} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584 > # > # JRE version: 7.0_25-b30 > # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2 > # > {code} > I'm running on Ubuntu 12.04. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13438) jboss-packaging-maven-plugin jboss-esb + m2e

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13438?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-13438: ------------------------------------- Manosh, this looks like a great contribution, thanks! However, feature patches are very unfriendly to work with. We don't see what's changed, you loose commit authorship and it's very hard to discuss changes on specific lines of code. Can you try to submit pull requests on github? See https://github.com/jbosstools/jbosstools-central/#contribute-fixes-and-fe... > jboss-packaging-maven-plugin jboss-esb + m2e > -------------------------------------------- > > Key: JBIDE-13438 > URL: https://issues.jboss.org/browse/JBIDE-13438 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: esb, integration-platform, maven > Reporter: Manosh C > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > Attachments: jboss-tools-m2e-esb-sar-sources.zip, test-m2e-esb-sar.zip, testparent.zip > > > Hi, > > Does jboss-packaging-maven-plugin m2e connector work for jboss-esb? When I import a maven jboss-esb project into eclipse (m2e installed), it does not covert it into an Eclipse JBoss ESB (facet is not enabled and dependecies are not set) project. I tried almost all versions of eclipse, m2e, jboss tools and jboss soa tools, to make it work, but no use. This is my work around for now > > 1. Turn on facet nature and enable JBOSS ESB nature. > 2. Then it get recognized as a deployable artifact on JBoss server. > 3. Manually add all dependencies in "Deployment and Assembly section". > > What I was expecting was all steps should have been done by m2e jboss esb (jboss-packaging-maven-plugin) connector. I could not find a relevant post or article related to it. Does this feature ever supported? > > Thank you in advance. > Manosh -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-16286 at 12/18/13 4:51 PM: -------------------------------------------------------------------- In my initial Eclipse, the build is still very slow. It's configuration is: * Kepler Service Release 1, Build id: 20130919-0819 * m2e: org.eclipse.m2e.core_1.5.0.20131218-1213 * cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524 Even after switching to new workspace this Eclipse is very slow in building. I attached it's full plugin-listing re-build though was equally fast as in the other Eclipse: * start: 22:44:31 * stop: 22:49:42 was (Author: adietish): In my initial Eclipse, the build is still very slow. It's configuration is: * Kepler Service Release 1, Build id: 20130919-0819 * m2e: org.eclipse.m2e.core_1.5.0.20131218-1213 * cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524 Even after switching to new workspace this Eclipse is very slow in building. I attached it's full plugin-listing > CDI builder (not import, workspace rebuild) is very slow in wildfly > ------------------------------------------------------------------- > > Key: JBIDE-16286 > URL: https://issues.jboss.org/browse/JBIDE-16286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.1.Final > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: performance > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png, VisualVM 1.3.2 _083.png > > > When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me. > Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me. > [^cdi-builder.ogv] -- 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, 3 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 December 2013