December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-16308. ---------------------------------- Resolution: Duplicate Issue > Cannot start JBT 4.2.0.Alpha1 on Fedora 19 > ------------------------------------------ > > Key: JBIDE-16308 > URL: https://issues.jboss.org/browse/JBIDE-16308 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, xulrunner > Affects Versions: 4.2.0.Alpha1 > Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7 > Reporter: Jiri Peterka > Priority: Blocker > Fix For: 4.2.0.Alpha2 > > Attachments: hs_err_pid17371.log, hs_err_pid18745.log > > > Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have: > {code} > !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > java.lang.OutOfMemoryError: GC overhead limit exceeded > at java.util.ArrayList.iterator(ArrayList.java:814) > at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962) > at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787) > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252) > at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652) > at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75) > at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412) > at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402) > at org.eclipse.osgi.container.Module.start(Module.java:406) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340) > {code} > Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written -- 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 Horst Duchene (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Horst Duchene commented on JBIDE-15185: --------------------------------------- I do not think taht the runtime detection dialog is the right place. Instead if I could enter a relative path or a path containing a variable in the "Jboss Runtime" dialog would help us. We want to save this configuration in subversion and distribute it to developers. The runtime is always at the same place relative to the checkout out project root. > 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-15185) add flexibility that JBoss runttime server uses variables instead of absolute path for the home directory.

by Horst Duchene (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15185?page=com.atlassian.jira.plugi... ] Horst Duchene edited comment on JBIDE-15185 at 12/20/13 1:43 AM: ----------------------------------------------------------------- I do not think that the runtime detection dialog is the right place. Instead, if I could enter a relative path or a path containing a variable in the "Jboss Runtime" dialog would help us. We want to save this configuration in subversion and distribute it to developers. The runtime is always at the same place relative to the checkout out project root. was (Author: horstduchene): I do not think taht the runtime detection dialog is the right place. Instead if I could enter a relative path or a path containing a variable in the "Jboss Runtime" dialog would help us. We want to save this configuration in subversion and distribute it to developers. The runtime is always at the same place relative to the checkout out project root. > 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-16317) Tag projects for jbosstools-4.2.0.Alpha1

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16317: ---------------------------------- Summary: Tag projects for jbosstools-4.2.0.Alpha1 Key: JBIDE-16317 URL: https://issues.jboss.org/browse/JBIDE-16317 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.0.Alpha1 Reporter: Nick Boldt Fix For: 4.2.0.Alpha1 Project leads, please tag your projects! {code} co jbosstools-4.2.0.Alpha1x git tag jbosstools-4.2.0.Alpha1 git push origin jbosstools-4.2.0.Alpha1 {code} -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16280: ------------------------------- Workaround Description: 1. Use Eclipse 4.4.0.M4 instead of M3 2. Use `export SWT_GTK3=0` before running Eclipse 3. Disable VPE from using Xulrunner using `-Dorg.jboss.tools.vpe.loadxulrunner=false` in your eclipse.ini's vmargs. was: 1. Use Eclipse 4.4.0.M4 instead of M3 2. Use `export SWT_GTK3=0` before running Eclipse 3. Disable VPE from using Xulrunner using `–Dorg.jboss.tools.vpe.loadxulrunner=false` in your eclipse.ini's vmargs. > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16280: ------------------------------- Workaround Description: 1. Use Eclipse 4.4.0.M4 instead of M3 2. Use `export SWT_GTK3=0` before running Eclipse 3. Disable VPE from using Xulrunner using `–Dorg.jboss.tools.vpe.loadxulrunner=false` in your eclipse.ini's vmargs. Workaround: Workaround Exists > 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-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16286: ---------------------------------------- [~adietish] any news about your workspace? Can we get it to reproduce the issue? :) > 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

[JBoss JIRA] (JBIDE-15373) Check all code run by builders for thread safety

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15373?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15373: ----------------------------------- Fix Version/s: 4.1.2.Final 4.2.0.Alpha2 (was: 4.2.x) > Check all code run by builders for thread safety > ------------------------------------------------ > > Key: JBIDE-15373 > URL: https://issues.jboss.org/browse/JBIDE-15373 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, common/jst/core, jsf > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > -- 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-15373) Check all code run by builders for thread safety

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15373?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15373: ----------------------------------------------- Fixed code that failed with a big probability at adding/removing CDI nature to projects in wildfly. (https://github.com/jbosstools/jbosstools-javaee/pull/188) > Check all code run by builders for thread safety > ------------------------------------------------ > > Key: JBIDE-15373 > URL: https://issues.jboss.org/browse/JBIDE-15373 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, common/jst/core, jsf > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > -- 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-16271) Support jquery mobile 1.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16271?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16271: ---------------------------------------- [~maxandersen] should we merge JQM Palette/code completion to 4.1.2.x too? > Support jquery mobile 1.4 > ------------------------- > > Key: JBIDE-16271 > URL: https://issues.jboss.org/browse/JBIDE-16271 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > Attachments: Combobox.bmml, Combobox.bmml, Combobox.png > > > jquery mobile 1.4 is coming out and apparently have performance fixes making it better suited for cordova development. > Noets from Vineet: > "I wouldn't say 1.4 is more compatible. It's a case of jQM 1.4 being more suitable > for Cordova apps. jQM 1.4 is more performant and thus Cordova apps are less sluggish. > The release notes allude to this: http://jquerymobile.com/blog/2013/09/24/announcing-jquery-mobile-1-4-beta/ > I've got no hard numbers here, but this slides in this talk - http://www.slideshare.net/AlexanderSchmitz/austin-26252266 > gives a better overview of what's in 1.4. Slide 22 is most relevant - > jQM 1.4 ships with a better default theme that improves performance, > among various other changes discussed in other slides." > Need to find out what issues jquery mobile palette and others might have with supporting jquery mobile for both 1.3 and 1.4...will be relevant with future new versions too. -- 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