November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-2450) JVM error occurs in Seam Core tests sometimes under Suse 10 (dev73-sles10)

by Denis Golovin (JIRA)

JVM error occurs in Seam Core tests sometimes under Suse 10 (dev73-sles10) -------------------------------------------------------------------------- Key: JBIDE-2450 URL: http://jira.jboss.com/jira/browse/JBIDE-2450 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Denis Golovin [echo] performing "ui" test on plugin "org.jboss.tools.seam.core.test" class "org.jboss.tools.seam.core.test.SeamCoreAllTests" ui-test: eclipse-test: [java] EMMA: collecting runtime coverage data ... [java] Reloaded 83 components in 61 ms!SESSION 2008-06-27 00:47:23.088 ----------------------------------------------- [java] eclipse.buildId=I20080530-1730 [java] java.version=1.5.0_14 [java] java.vendor=Sun Microsystems Inc. [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US [java] Framework arguments: -application org.eclipse.test.uitestapplication -plugincustomization /home/hudson/hudson_workspace/workspace/jbosstools-nightly/org.jboss.ide.eclipse.releng/builders/tests/plugin_customization.ini formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,org.jboss.tools.seam.core.test.SeamCoreAllTests.xml -testPluginName org.jboss.tools.seam.core.test -classname org.jboss.tools.seam.core.test.SeamCoreAllTests [java] Command-line arguments: -application org.eclipse.test.uitestapplication -dev bin -data /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/workspace -plugincustomization /home/hudson/hudson_workspace/workspace/jbosstools-nightly/org.jboss.ide.eclipse.releng/builders/tests/plugin_customization.ini formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,org.jboss.tools.seam.core.test.SeamCoreAllTests.xml -testPluginName org.jboss.tools.seam.core.test -classname org.jboss.tools.seam.core.test.SeamCoreAllTests -consolelog [java] !ENTRY org.eclipse.wst.internet.cache 1 0 2008-06-27 00:49:51.397 [java] !MESSAGE wtp.autotest.noninteractive is set. Licenses dialogs will not be displayed. [java] -->100 SeamWebWarTestProject:p.p6.p12.p18.p24.p156.p162.T166 [java] -->200 SeamWebWarTestProject:p.p6.p12.p18.p24.p240.p264.T266 [java] -->300 SeamWebWarTestProject:p.p6.p12.p18.p282.T282 [java] -->400 SeamWebWarTestProject:p.p6.p12.p18.p282.p372.p378.T382 [java] -->500 SeamWebWarTestProject:p.p6.p12.p18.p282.p456.p480.T482 [java] -->600 SeamWebWarTestProject:p.p6.p12.p18.p540.p546.p582.T582 [java] -->700 SeamWebWarTestProject:p.p6.p12.p18.p540.p672.p678.T682 [java] -->800 SeamWebWarTestProject:p.p6.p12.p18.p540.p756.p780.T782 [java] -->900 SeamWebWarTestProject:p.p6.p12.p18.p798.p846.p882.T882 [java] -->1000 SeamWebWarTestProject:p.p6.p12.p18.p798.p972.p978.T982 [java] Full build of 1106 components completed in 19272ms [java] Reloaded 1106 components in 1032ms [java] First 200 paths are loaded in 71ms [java] Last 200 paths are loaded in 45ms [java] Listing /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam [java] 0: changelog.txt [java] 1: seam-text.g [java] 2: lgpl.txt [java] 3: drools (dir) [java] 4: microcontainer (dir) [java] 5: src (dir) [java] 6: examples (dir) [java] 7: embedded-ejb (dir) [java] 8: build.xml [java] 9: jboss-seam.jar [java] 10: hibernate (dir) [java] 11: jboss-seam-pdf.jar [java] 12: jboss-seam-remoting.jar [java] 13: jboss-seam-ioc.jar [java] 14: jboss-seam-mail.jar [java] 15: build.properties [java] 16: mail (dir) [java] 17: lib (dir) [java] 18: jboss-seam-ui.jar [java] 19: jboss-seam-debug.jar [java] 20: seam.bat [java] 21: seam-gen (dir) [java] 22: seam [java] 23: jboss-seam-gen.jar [java] Listing seamgen /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam/seam-gen [java] 0: view (dir) [java] 1: test (dir) [java] 2: src (dir) [java] 3: resources (dir) [java] 4: lib (dir) [java] 5: hibernatetools (dir) [java] 6: build.xml [java] 7: build-scripts (dir) [java] 8: USAGE [java] 9: README [java] 10: pojo (dir) [java] 11: nbproject (dir) [java] Deleting P/seamwar [java] Deleting P/seamwar-test [java] Listing /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam [java] 0: changelog.txt [java] 1: seam-text.g [java] 2: lgpl.txt [java] 3: drools (dir) [java] 4: microcontainer (dir) [java] 5: src (dir) [java] 6: examples (dir) [java] 7: embedded-ejb (dir) [java] 8: build.xml [java] 9: jboss-seam.jar [java] 10: hibernate (dir) [java] 11: jboss-seam-pdf.jar [java] 12: jboss-seam-remoting.jar [java] 13: jboss-seam-ioc.jar [java] 14: jboss-seam-mail.jar [java] 15: build.properties [java] 16: mail (dir) [java] 17: lib (dir) [java] 18: jboss-seam-ui.jar [java] 19: jboss-seam-debug.jar [java] 20: seam.bat [java] 21: seam-gen (dir) [java] 22: seam [java] 23: jboss-seam-gen.jar [java] Listing seamgen /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam/seam-gen [java] 0: view (dir) [java] 1: test (dir) [java] 2: src (dir) [java] 3: resources (dir) [java] 4: lib (dir) [java] 5: hibernatetools (dir) [java] 6: build.xml [java] 7: build-scripts (dir) [java] 8: USAGE [java] 9: README [java] 10: pojo (dir) [java] 11: nbproject (dir) [java] Deleting P/seamear-ear [java] Deleting P/seamear-ejb [java] Deleting P/seamear-test [java] Deleting P/seamear [java] Listing /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam [java] 0: changelog.txt [java] 1: seam-text.g [java] 2: lgpl.txt [java] 3: drools (dir) [java] 4: microcontainer (dir) [java] 5: src (dir) [java] 6: examples (dir) [java] 7: embedded-ejb (dir) [java] 8: build.xml [java] 9: jboss-seam.jar [java] 10: hibernate (dir) [java] 11: jboss-seam-pdf.jar [java] 12: jboss-seam-remoting.jar [java] 13: jboss-seam-ioc.jar [java] 14: jboss-seam-mail.jar [java] 15: build.properties [java] 16: mail (dir) [java] 17: lib (dir) [java] 18: jboss-seam-ui.jar [java] 19: jboss-seam-debug.jar [java] 20: seam.bat [java] 21: seam-gen (dir) [java] 22: seam [java] 23: jboss-seam-gen.jar [java] Listing seamgen /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam/seam-gen [java] 0: view (dir) [java] 1: test (dir) [java] 2: src (dir) [java] 3: resources (dir) [java] 4: lib (dir) [java] 5: hibernatetools (dir) [java] 6: build.xml [java] 7: build-scripts (dir) [java] 8: USAGE [java] 9: README [java] 10: pojo (dir) [java] !ENTRY org.eclipse.jdt.core 4 969 2008-06-27 00:52:47.290 [java] !MESSAGE seamear-ejb does not exist [java] 11: nbproject (dir) [java] !ENTRY org.eclipse.jdt.core 4 969 2008-06-27 00:52:47.292 [java] !MESSAGE seamear does not exist [java] Listing /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam [java] 0: changelog.txt [java] 1: seam-text.g [java] 2: lgpl.txt [java] 3: drools (dir) [java] 4: microcontainer (dir) [java] 5: src (dir) [java] 6: examples (dir) [java] 7: embedded-ejb (dir) [java] 8: build.xml [java] 9: jboss-seam.jar [java] 10: hibernate (dir) [java] 11: jboss-seam-pdf.jar [java] 12: jboss-seam-remoting.jar [java] 13: jboss-seam-ioc.jar [java] 14: jboss-seam-mail.jar [java] 15: build.properties [java] 16: mail (dir) [java] 17: lib (dir) [java] 18: jboss-seam-ui.jar [java] 19: jboss-seam-debug.jar [java] 20: seam.bat [java] 21: seam-gen (dir) [java] 22: seam [java] 23: jboss-seam-gen.jar [java] Listing seamgen /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/jboss/jboss-eap-4.3/seam/seam-gen [java] 0: view (dir) [java] 1: test (dir) [java] 2: src (dir) [java] 3: resources (dir) [java] 4: lib (dir) [java] 5: hibernatetools (dir) [java] 6: build.xml [java] 7: build-scripts (dir) [java] 8: USAGE [java] 9: README [java] 10: pojo (dir) [java] 11: nbproject (dir) [java] # [java] # An unexpected error has been detected by HotSpot Virtual Machine: [java] # [java] # SIGBUS (0x7) at pc=0xb756eb43, pid=28951, tid=1961348000 [java] # [java] # Java VM: Java HotSpot(TM) Client VM (1.5.0_14-b03 mixed mode) [java] # Problematic frame: [java] # C [libzip.so+0xbb43] [java] # [java] # An error report file with more information is saved as hs_err_pid28951.log [java] # [java] # If you would like to submit a bug report, please visit: [java] # http://java.sun.com/webapps/bugreport/crash.jsp [java] # [java] Java Result: 134 [echo] Copy .log files to /home/hudson/hudson_workspace/workspace/jbosstools-nightly/org.jboss.ide.eclipse.releng/../jvmerrors [copy] Copying 1 file to /home/hudson/hudson_workspace/workspace/JBossTools/jvmerrors [mkdir] Created dir: /home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/test-results/emma-coverage [merge] processing input files ... [merge] 2 file(s) read and merged in 1029 ms [merge] merged/compacted data written to [/qa/services/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/test-results/emma-coverage/coverage.es] {in 265 ms} [report] processing input files ... [report] 1 file(s) read and merged in 514 ms [report] writing [xml] report to [/home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/coverage.xml] ... [report] writing [html] report to [/home/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806262311-nightly/tests/test-results/emma-coverage/index.html] ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-5508) Main class for Server launch uses Project instead of related classpath for search

by Max Rydahl Andersen (JIRA)

Main class for Server launch uses Project instead of related classpath for search --------------------------------------------------------------------------------- Key: JBIDE-5508 URL: https://jira.jboss.org/jira/browse/JBIDE-5508 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M4 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.1.0.GA, 3.2.next There is a Project field on the main class of the server - what is that for ? The search seem to use it, but that doesn't have any relevance to what is on the classpath of the server. i.e. the default class is not available when searching. Marked critical for usability and possible sideeffects of storing project location in the launch config. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1311) pack2000 errors related to jars inside modeshape component

by Denis Golovin (JIRA)

pack2000 errors related to jars inside modeshape component ---------------------------------------------------------- Key: JBDS-1311 URL: https://jira.jboss.org/browse/JBDS-1311 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build Affects Versions: 4.0.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Fix For: 4.0.0.M2 it started to report problems after processing for WEB-INF/lib/lucene-core-3.0.0.jar started inside org.jboss.tools.modeshape.rest_1.0.0.v201009071649N-M2/modeshape-web-jcr-rest-client-2.1-SNAPSHOT-jar-with-dependencies.jar Processing nested file: WEB-INF/lib/lucene-core-3.0.0.jar [pack200] STDOUT: Legacy package version [pack200] STDOUT: not found: Utf8=Index [pack200] STDOUT: in: Index Utf8 [4084] { [pack200] STDOUT: 0: Utf8= looks like lucene started to index something (see STDOUT messages after snipped above) That's probably a reason of further instrumentation error [echo] Applying Seam-gen Patch [echo] Move emma jars to /home/eskimo/Projects/jbds-build-4.0.0.M2/jbds-build/4.0.0.M2/201009071649/tests/eclipse [copy] Copying 1 file to /home/eskimo/Projects/jbds-build-4.0.0.M2/jbds-build/4.0.0.M2/201009071649/tests/eclipse [echo] portlet,examples,smooks,esb,freemarker,birt,as,archives,hibernate-tools,common,jsf,jst,struts,seam,vpe,ws,modeshape,jmx,jbpm-convert,cdi [echo] Run tests for portlet [mkdir] Created dir: /home/eskimo/Projects/jbds-build-4.0.0.M2/jbds-build/4.0.0.M2/201009071649/tests/test-results/emma-coverage/portlet [instr] processing instrumentation path ... BUILD FAILED /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:18: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/build.xml:68: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/build.xml:39: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:106: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:186: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/tests/testBuild.xml:142: The following error occurred while executing this line: /home/eskimo/Projects/jbds-build-4.0.0.M2/org.jboss.ide.eclipse.releng/builders/tests/testBuild.xml:146: com.vladium.emma.EMMARuntimeException: com.vladium.emma.EMMARuntimeException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7745) Seam/JSF UI test fails on b2

by Max Andersen (JIRA)

Seam/JSF UI test fails on b2 ---------------------------- Key: JBIDE-7745 URL: https://jira.jboss.org/browse/JBIDE-7745 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Andersen Assignee: Max Andersen Priority: Critical Fix For: 3.2.0.Beta2, 3.2.0.CR1 see http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/portlet/da... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

6
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7320) create unit test

by Andre Dietisheim (JIRA)

create unit test ---------------- Key: JBIDE-7320 URL: https://jira.jboss.org/browse/JBIDE-7320 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 We need unit test to test the code units. The tests should use its own (internal) deltacloud that runs in the same JVM (on top of JRuby) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
16
0 / 0

[JBoss JIRA] Created: (JBIDE-7321) create integration tests

by Andre Dietisheim (JIRA)

create integration tests ------------------------ Key: JBIDE-7321 URL: https://jira.jboss.org/browse/JBIDE-7321 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.Beta2 we need integration tests that helps us to detect api changes in deltacloud. Ideally we'd use the deltacloud instance the stormgrinder guys use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-1530) Integrate the automatic migration of old packaging

by Max Andersen (JIRA)

Integrate the automatic migration of old packaging -------------------------------------------------- Key: JBIDE-1530 URL: http://jira.jboss.com/jira/browse/JBIDE-1530 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Archives Affects Versions: 2.0.0.GA Reporter: Max Andersen Assigned To: Marshall Culpepper Fix For: 2.1 have a context menu option available on projects that has an .packaging file in it ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-3549) Providing APIs for getting the output message of the jboss server through WTP server adaptor

by Denny Xu (JIRA)

Providing APIs for getting the output message of the jboss server through WTP server adaptor --------------------------------------------------------------------------------------------- Key: JBIDE-3549 URL: https://jira.jboss.org/jira/browse/JBIDE-3549 Project: Tools (JBoss Tools) Issue Type: Task Components: JBossAS Affects Versions: LATER Reporter: Denny Xu Assignee: Rob Stryker Rob, I am trying to develop a Test UI for ESB service, I would like to have APIs to get the console output of a running server so that I can show the result message on TestUI page after a Test action is executed. since there might be a lot of application running on the server, and there maybe a lots of outputs during a period , so if we can only get the output of a specified application, that would be better. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6174) Folding of exceptions in Console tab

by Ryszard Kozmik (JIRA)

Folding of exceptions in Console tab ------------------------------------ Key: JBIDE-6174 URL: https://jira.jboss.org/jira/browse/JBIDE-6174 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Ryszard Kozmik It would be really helpful to read server logs if exceptions were folded into one line with a plus symbol next to it that would show the whole exception on a click. As we all know sometimes apps are very "talkactive" in case of throwing exceptions and browsing through them to find the exact one that you search for is irritating and folding would greatly help. It can be even a simple folding based on indentation of lines, you can do such set up with GVIM / VIM but it's not so convenient to use and first of all it's not in your favourite IDE ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7732) fixe for JBIDE-1029 breaks version control for SCM that reqiure checkout for writable files

by joe freeman (JIRA)

fixe for JBIDE-1029 breaks version control for SCM that reqiure checkout for writable files ------------------------------------------------------------------------------------------- Key: JBIDE-7732 URL: https://jira.jboss.org/browse/JBIDE-7732 Project: Tools (JBoss Tools) Issue Type: Bug Components: jbpm Affects Versions: 3.2.0.M2 Environment: Eclipse 3.6 with JBPM 3 editor 3.2.0M2 probably introduced in 3.1 M3 Reporter: joe freeman Assignee: Koen Aers Priority: Critical JBIDE-1029 tried to fix the issue where the JBPM xml editor fails when editing non-writable files. The fix (015307?) in the URL below offers the user the opportunity to change the attributes from r/o to r/w bypassing the SCM hooks. So for an SCM like Perforce where all files are locked until checkout, the user will have changed the R/W bits without notifying the SCM so they can save their changes but they never get committed back to the repository. Users can lose changes without knowing it. If you answer NO to the panel offered by JBIDE-1029 then the editor will still let you edit and when you save it will check out the processdefinition.xml in the SCM file like it used to and will fail on the gpd and jpg files (like it used to). The fix should have used the same Eclipse hooks used by the editor so that all 3 files end up checked out. Changing the access bits directly seems like a bad idea http://lists.jboss.org/pipermail/jbosstools-commits/2009-September/015307... https://jira.jboss.org/browse/JBIDE-1029 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
10
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 November 2010