December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16311) release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16311?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16311: ------------------------------------ http://download.jboss.org/jbosstools/updates/webtools/luna/ is now populated with 4.2.0.Alpha1-v20131211-0610-B31. Once the upstream is fixed in a new version of Eclipse Luna JEE, this issue can be verified and closed (using Luna M5). > release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it > --------------------------------------------------------------------------- > > Key: JBIDE-16311 > URL: https://issues.jboss.org/browse/JBIDE-16311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha1 > > Attachments: eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png, eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png > > > Need a semi-working placeholder (even if it's a weak first alpha) so that WTP can resolve http://download.jboss.org/jbosstools/updates/webtools/luna/ as a valid site. > Content that needs to be verified (install tested) and renamed is here: > http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webt... > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=424213 -- 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-16311) release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16311?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16311: ------------------------------- Attachment: eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png Entire site (all categorized and uncategorized features) installed into eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz and did not crash. Did not have to tweak memory settings or use and GTK3=0 flag to prevent coredump / halt / crash. After warm restart, these servers were available: !eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png! And I could create a connection to the EAP 6.1+ server I have in /home/nboldt/tmp/jboss-runtimes/jboss-eap-6.2: !eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png! > release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it > --------------------------------------------------------------------------- > > Key: JBIDE-16311 > URL: https://issues.jboss.org/browse/JBIDE-16311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Alpha1 > > Attachments: eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1.png, eclipse44-installed-all-features-from jbt-wtp-site-4.2.0.Alpha1_2.png > > > Need a semi-working placeholder (even if it's a weak first alpha) so that WTP can resolve http://download.jboss.org/jbosstools/updates/webtools/luna/ as a valid site. > Content that needs to be verified (install tested) and renamed is here: > http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webt... > Upstream issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=424213 -- 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-16311) release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16311: ---------------------------------- Summary: release 4.2.0.Alpha1 webtools site to so WTP discovery upstream can find it Key: JBIDE-16311 URL: https://issues.jboss.org/browse/JBIDE-16311 Project: Tools (JBoss Tools) Issue Type: Bug Components: server, updatesite Affects Versions: 4.2.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.2.0.Alpha1 Need a semi-working placeholder (even if it's a weak first alpha) so that WTP can resolve http://download.jboss.org/jbosstools/updates/webtools/luna/ as a valid site. Content that needs to be verified (install tested) and renamed is here: http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.webt... Upstream issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=424213 -- 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-16309) Move inter-JBT dependencies to component poms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16309: ---------------------------------------- You're probably right, I'll prepare a mail for the team. > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16309: ------------------------------------ +0.9. Seems reasonable but maybe we should get buy in from all the project leads FIRST rather than just decreeing "this is the new way forward?" > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.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

12 years, 3 months

1
0
0 / 0

cannot find ManagementRequestHandlerFactory

by Mathieu Petit

Dear all, I'm trying to run JBossTools in Eclispe Kepler with Wildfly 8.0 server. Adding a server went well, but when I try to start the server from inside eclipse, jbosstools complains : An internal error occurred during: "Starting WildFly 8.0 Runtime 1 Server". org/jboss/as/protocol/mgmt/ManagementRequestHandlerFactory From Eclipse logfile, it seems a jar is missing : !ENTRY org.eclipse.core.jobs 4 2 2013-12-17 17:34:45.511 !MESSAGE An internal error occurred during: "Starting WildFly 8.0 Runtime 1 Server". !STACK 0 java.lang.NoClassDefFoundError: org/jboss/as/protocol/mgmt/ManagementRequestHandlerFactory at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188) .... Can someone help ? Best regards, Mathieu

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16309) Move inter-JBT dependencies to component poms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16309?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16309: ---------------------------------------- [~nickboldt] [~dgolovin] [~maxandersen] I'd be glad if we could adopt this approach ASAP. Can you please +1/-1 this issue? If you're OK with this I'll: # Make PR on each component to add the repositories in the pom.xml, and when all are merged # Remove the jbosstools-site profile and related properties from parent pom. > Move inter-JBT dependencies to component poms > --------------------------------------------- > > Key: JBIDE-16309 > URL: https://issues.jboss.org/browse/JBIDE-16309 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > It has been discussed several times that the composite site is a kind of "weak point" in our build chain, because it allows cyclic dependencies, and it also introduces indirections that make it less straightforward to find out what a project should/does depend on to build. > The benefit of composite now seem a bit light: it's cool because we can put it in parent pom and all builds succeed to get there dependencies, but out of that, there hasn't been much other use-cases. And as we want to provide more and more autonomy to project, this composite site they'd depend on is something that doesn't make them autonomous. > So the idea is to move dependencies to project root poms. I've made a draft of how it would look like in project pom if we remove the "jbosstools-site" from parent pom and let projects manage their inter-dependencies: https://github.com/mickaelistria/jbosstools-javaee/tree/JBIDE-16309 > You can try this by running "mvn clean verify -P\!jbosstools-site". The "-P\!jbosstools-site" disable the jbosstools-site profile, which is the one controlling addition of the composite or ggregate to the resolver > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.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

12 years, 3 months

1
0
0 / 0

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

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16280: --------------------------------------- I think SWT GTK2 is stable. Eclipse will support it for a long time so the best solution would probably be to set the old XULRunner to GTK2 as optional until the VPE editor is ported to webkit or we find some other solution. > 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.Alpha1 > > Attachments: hs_err_pid20688.log > > > 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 Alexander Kurtakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugi... ] Alexander Kurtakov commented on JBIDE-16280: -------------------------------------------- Xulrunner is not ported to GTK 3 itself. There is not much eclipse can do about it. Plus Xulrunner itself no longer provides any notion of stable API so SWT will always support some limited version number until people get tired of constantly fixing compatibility with the next version. See http://www.eclipse.org/swt/faq.php#browserlinux for list of suppported versions. Fedora currently ships with Xulrunner 25.0 and in the Eclipse package shipped with fedora swt/xulrunner intergration is not compiled in as noone has any interest in fixing it. Speaking with my SWT hat on lobbying at Eclipse would not make a difference unless this lobbying comes with patches as the number of pending issues are way more important than xulrunner. > 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.Alpha1 > > Attachments: hs_err_pid20688.log > > > 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-2720) Need 64-bit windows support

by Carsten Pfeiffer (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Carsten Pfeiffer commented on JBIDE-2720: ----------------------------------------- [~kmarmaliykov] Yes, this patch is for xulrunner. It changes the link process for the javascript library in xulrunner to add a manifest to the resulting dll. You don't actually need to rebuild all of xulrunner. You could also manually invoke mt.exe to add the manifest (which is being created during build, but not added to the dll). For details see http://msdn.microsoft.com/en-us/library/ms235591.aspx If this is too uncomfortable for you, you can just rebuild xulrunner with the patch applied. [~dagz213] I don't have the time to explain how to build the entire xulrunner, but there is plenty of information from Mozilla. See e.g. https://developer.mozilla.org/en-US/docs/Developer_Guide/Source_Code and https://developer.mozilla.org/en-US/docs/Configuring_Build_Options for a start. > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Konstantin Marmalyukov > Fix For: 4.2.x > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for Windows 64-bit. > *Update:* > In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... > {color:red}*Known problems:*{color} > * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK > *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:* > * Try to uninstall Intel OpenCL SDK > * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio) > If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library. -- 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