September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9565) compile fialed in org.jboss.tools.deltacloud.ui.bot.test :: The import org.jboss.tools.ui.bot.ext.config.Annotations.SWTBotTestRequires cannot be resolved

by Nick Boldt (JIRA)

compile fialed in org.jboss.tools.deltacloud.ui.bot.test :: The import org.jboss.tools.ui.bot.ext.config.Annotations.SWTBotTestRequires cannot be resolved ---------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9565 URL: https://issues.jboss.org/browse/JBIDE-9565 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud, testing Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Andre Dietisheim Fix For: 3.3.0.M3 http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3... [INFO] deltacloud.all .................................... SUCCESS [0.454s] [INFO] deltacloud.plugins ................................ SUCCESS [0.009s] [INFO] org.jboss.tools.deltacloud.core ................... SUCCESS [7.409s] [INFO] org.jboss.tools.deltacloud.ui ..................... SUCCESS [7.265s] [INFO] org.jboss.tools.deltacloud.docs ................... SUCCESS [0.912s] [INFO] org.jboss.tools.deltacloud.integration ............ SUCCESS [1.923s] [INFO] deltacloud.features ............................... SUCCESS [0.011s] [INFO] org.jboss.tools.deltacloud.feature ................ SUCCESS [0.299s] [INFO] deltacloud.tests .................................. SUCCESS [0.012s] [INFO] org.jboss.tools.deltacloud.test ................... SUCCESS [1.201s] [INFO] org.jboss.tools.deltacloud.ui.bot.test ............ FAILURE [1.422s] [INFO] org.jboss.tools.deltacloud.test.feature ........... SKIPPED [INFO] deltacloud.site ................................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.12.0:compile (default-compile) on project org.jboss.tools.deltacloud.ui.bot.test: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--deltacloud/sources/tests/org.jboss.tools.deltacloud.ui.bot.test/src/org/jboss/tools/deltacloud/ui/bot/test/CloudViewerTest.java (at line 9):[-1,-1] [ERROR] import org.jboss.tools.ui.bot.ext.config.Annotations.SWTBotTestRequires; [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The import org.jboss.tools.ui.bot.ext.config.Annotations.SWTBotTestRequires cannot be resolved [ERROR] [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--deltacloud/sources/tests/org.jboss.tools.deltacloud.ui.bot.test/src/org/jboss/tools/deltacloud/ui/bot/test/CloudViewerTest.java (at line 14):[-1,-1] [ERROR] @SWTBotTestRequires(runOnce=true,perspective="Deltacloud",secureStorage=true) [ERROR] ^^^^^^^^^^^^^^^^^^ [ERROR] SWTBotTestRequires cannot be resolved to a type -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9378) test failure(s) in common: org.jboss.tools.common.verification.ui.test :: org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]

by Nick Boldt (JIRA)

test failure(s) in common: org.jboss.tools.common.verification.ui.test :: org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9378 URL: https://issues.jboss.org/browse/JBIDE-9378 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, testing Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Attachments: console.log.txt [INFO] org.jboss.tools.common.verification.ui.test ....... FAILURE [12.416s] [ERROR] Please refer to /mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.component--common/sources/tests/org.jboss.tools.common.verification.ui.test/target/surefire-reports for the individual test results. There is no report, because the test failed before it could record results. Here's the console log, captured here: https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--co... (See attached.) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-9441) NPE during seam.ui tests running

by Alexey Kazakov (JIRA)

NPE during seam.ui tests running -------------------------------- Key: JBIDE-9441 URL: https://issues.jboss.org/browse/JBIDE-9441 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x {code} java.lang.NullPointerException at org.jboss.tools.jst.web.kb.internal.KbProject.getStorageFile(KbProject.java:429) at org.jboss.tools.jst.web.kb.internal.KbProject.store(KbProject.java:410) at org.jboss.tools.jst.web.kb.WebKbPlugin$1.saving(WebKbPlugin.java:62) at org.eclipse.core.internal.resources.SaveManager.executeLifecycle(SaveManager.java:382) at org.eclipse.core.internal.resources.SaveManager$1.run(SaveManager.java:191) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.resources.SaveManager.broadcastLifecycle(SaveManager.java:194) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1129) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1108) at org.eclipse.core.internal.resources.DelayedSnapshotJob.run(DelayedSnapshotJob.java:51) at org.eclipse.core.internal.resources.SaveManager.shutdown(SaveManager.java:1390) at org.eclipse.core.internal.resources.Workspace.close(Workspace.java:604) at org.eclipse.core.resources.ResourcesPlugin.stop(ResourcesPlugin.java:415) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:771) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(BundleContextImpl.java:764) at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(BundleHost.java:510) at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:565) at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1160) at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(StartLevelManager.java:595) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:257) at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:215) at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.suspend(InternalSystemBundle.java:284) at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:690) at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:597) at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:390) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:198) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9430) JBT 3.3 aggregate build failed: results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize()

by Nick Boldt (JIRA)

JBT 3.3 aggregate build failed: results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize() -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9430 URL: https://issues.jboss.org/browse/JBIDE-9430 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M3 [xslt] mnt/hudson_workspace/workspace/jbosstools-3.3_trunk.aggregate/sources/results/buildResults.xsl:200: Fatal Error! A sequence of more than one item is not allowed as the first argument of tokenize() ("http://anonsvn.jboss.org/repos...", "http://anonsvn.jboss.org/repos...") https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/333... Possible solution: {code} diff --git a/build/results/buildResults.xsl b/build/results/buildResults.xsl index 27346f1..da19686 100644 --- a/build/results/buildResults.xsl +++ b/build/results/buildResults.xsl @@ -197,7 +197,7 @@ </li> <xsl:for-each - select="tokenize(//property[contains(@name,'build.properties.SVN_REVISION') and contains(@name,$COMPONENT)]/@value,',')"> + select="tokenize(//property[contains(@name,'build.properties.SVN_REVISION') and contains(@name,$COMPONENT)][1]/@value,',')"> <li>SVN: <xsl:value-of select="." /></li> </xsl:for-each> </ul> {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)

by Juergen Zimmermann (JIRA)

Runtimes are not configurable (JBIDE-1354) ------------------------------------------ Key: JBIDE-9605 URL: https://issues.jboss.org/browse/JBIDE-9605 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.3.0.M2 Reporter: Juergen Zimmermann Assignee: Snjezana Peco JBIDE-1354 should provide the possibility to save runtime configurations. These configurations are stored in the paths .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/runtimeClasspaths/org.jboss.ide.eclipse.as.runtime.32 etc. However, there is only the path .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/default and additions to a runtime like "JBoss 7.x Runtime" are not possible. If I manually create the path .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/runtimeClasspaths, then a new entry can be added and there is e.g. org.jboss.ide.eclipse.as.runtime.70. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-5720) EAR Libraries in Dynamic Web Project

by Burr Sutter (JIRA)

EAR Libraries in Dynamic Web Project ------------------------------------ Key: JBIDE-5720 URL: https://jira.jboss.org/jira/browse/JBIDE-5720 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: core Environment: jbdevstudio-win32-3.0.0.v201001060655N-H50-CR1 Reporter: Burr Sutter Attachments: EAR_Libraries.jpg Creation of a New Dynamic Web Project adds "EAR Libraries" - that does not make sense because I (the user) am building a WAR and I do not want anything to do with an EAR in this case. -- 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

14 years, 7 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1354) Runtimes should be configurable with respect to what jars to return for certain runtimes

by Max Andersen (JIRA)

Runtimes should be configurable with respect to what jars to return for certain runtimes ---------------------------------------------------------------------------------------- Key: JBIDE-1354 URL: http://jira.jboss.com/jira/browse/JBIDE-1354 Project: JBoss Tools Issue Type: Feature Request Components: JBossAS Reporter: Max Andersen Fix For: 2.1 deploy only runtime could have preferences to control which jars they would actually return for various facets etc. optimally these would actually work on on any of our runtimes and just use variables/clever-defaults depending and allow users to override them if necessary. The user should be able to point to jars in a project, workspace, filesystem, classpath library, maven/ivy dependency even ...etc. -- 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

14 years, 7 months

6
26
0 / 0

[JBoss JIRA] Created: (JBIDE-4127) "Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath

by Leiv Hellebo (JIRA)

"Add JSF-Capabilities" adds jsf-facelets.jar which is older than the one in .classpath -------------------------------------------------------------------------------------- Key: JBIDE-4127 URL: https://jira.jboss.org/jira/browse/JBIDE-4127 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.0.0.GA Environment: JBDS 2.0.GA Seam 2.1.X Reporter: Leiv Hellebo The Add JSF-Capabilities dialog makes it possible to shoot oneself in the foot: It will happily add jsf-facelets.jar with Implementation-Version: 1.1.11, even if the one mentioned in .classpath has Implementation-Version: 1.1.15.B1 AFAICS, when performing a redirect within a long-running conversation, this makes "DEBUG [org.jboss.seam.contexts.ServletLifecycle] >>> Begin re-initialization" disappear from server.log, and needed context vars are not initialized. I'd file this as an "Improvement", not a "Bug" if it was possible. You may want to say "PEBKAC" to this... -- 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

14 years, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-1050) Add Capabilities to Struts 1.3 at struts Tools

by Hermes Waldemarin (JIRA)

Add Capabilities to Struts 1.3 at struts Tools ---------------------------------------------- Key: JBIDE-1050 URL: http://jira.jboss.com/jira/browse/JBIDE-1050 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: Eclipse 3.3 Europa, Windows XP Reporter: Hermes Waldemarin I`m use struts 1.3.x in my aplication. I need to use chains policies in struts config, but this implementation is in 1.3.x version. Can you add Struts 1.3.x capabilities for struts plugin? Thanks... -- 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

14 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9268) Align versions across poms on each module

by Max Rydahl Andersen (JIRA)

Align versions across poms on each module ----------------------------------------- Key: JBIDE-9268 URL: https://issues.jboss.org/browse/JBIDE-9268 Project: Tools (JBoss Tools) Issue Type: Bug Components: Cleanup, Build/Releng Reporter: Max Rydahl Andersen Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.3.0.M3 We recently aligned the pom's within each jboss tools module svn to have "natural parents" meaning the only pom within a module that refers the parent pom is the "root" one. i.e. hibernatetools/pom.xml instead of *all* plugins and features inside the module. That made updating parent pom's easy, now we should just get the pom versions aligned within the module to allow easy update of versions in that module without manual tweaking of files. What this allows is that you can use commands like this: mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.4.0-SNAPSHOT and tycho will take care of updating all pom/manifest/feature.xml/product defs for that module subdirectory. (if the references are *outside* that directory then of course things won't be updated automatically) The changes i'm planning will do two things: 1) Align all versions within one module (that is needed for the one command version update) 2) Remove all redundant <version> references when the parent reference is enough. Please note, that if a module owner wish to manage individual plugin versions that is perfectly still doable they just need to add the explicit <version> reference and cannot rely on the one command version update to work automatically. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
6
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 September 2011