September 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9429) JBoss AS Runtime detector doesn't detect correctly JBoss AS 6.1/7.1 version

by Snjezana Peco (JIRA)

JBoss AS Runtime detector doesn't detect correctly JBoss AS 6.1/7.1 version --------------------------------------------------------------------------- Key: JBIDE-9429 URL: https://issues.jboss.org/browse/JBIDE-9429 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.3.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M3 Attachments: runtime.png See the attached screenshot. -- 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-7993) Configure->Add JSF Capabilities does not add JSF Facet

by Yahor Radtsevich (JIRA)

Configure->Add JSF Capabilities does not add JSF Facet ------------------------------------------------------ Key: JBIDE-7993 URL: https://issues.jboss.org/browse/JBIDE-7993 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Yahor Radtsevich STEPS TO REPRODUCE: 1. Create new Dynamic Web Project. 2. Right-click->Configure->Add JSF Capabilities on the project in the Package Expolorer view->Finish. 3. Open the project properties->Project Facets. ACTUAL RESULT: JSF Facet is not checked (screenshot-1.png). EXPECTED RESULT: JSF Facet is checked. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-5901) Add JSF capabilities asks a lot of questions and uses *absolute* filepaths

by Max Rydahl Andersen (JIRA)

Add JSF capabilities asks a lot of questions and uses *absolute* filepaths -------------------------------------------------------------------------- Key: JBIDE-5901 URL: https://jira.jboss.org/jira/browse/JBIDE-5901 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Fix For: 3.1.1, 3.2.next When Adding JSF support to an existing project i'm asked about *alot* of questions which seems irrelevant/outofdate plus it lists absolute file names. Web Root is fair to ask about, but why the full path ? Source and classes folder should be a given when its a Java Project anyway ? lib folder ? no idea what that is. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBIDE-9394) BuilderOrderValidationTest.testWrongBuildOrderPreference() failure

by Alexey Kazakov (JIRA)

BuilderOrderValidationTest.testWrongBuildOrderPreference() failure ------------------------------------------------------------------ Key: JBIDE-9394 URL: https://issues.jboss.org/browse/JBIDE-9394 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x This test fails from time to time. I can say in my computer it happens ~ every 20th time ;) {code} ------------------------------------------------------- T E S T S ------------------------------------------------------- Running org.jboss.tools.cdi.core.test.CDICoreAllTests Tests run: 350, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 509.015 sec <<< FAILURE! testWrongBuildOrderPreference(org.jboss.tools.cdi.core.test.tck.validation.BuilderOrderValidationTest) Time elapsed: 0.748 sec <<< FAILURE! junit.framework.AssertionFailedError: expected:<2> but was:<3> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:195) at junit.framework.Assert.assertEquals(Assert.java:201) at org.jboss.tools.cdi.core.test.tck.validation.BuilderOrderValidationTest.testWrongBuildOrderPreference(BuilderOrderValidationTest.java:82) ... {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
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9380) IncrementalValidationTest.testAlternativesInBeansXml() failure

by Alexey Kazakov (JIRA)

IncrementalValidationTest.testAlternativesInBeansXml() failure -------------------------------------------------------------- Key: JBIDE-9380 URL: https://issues.jboss.org/browse/JBIDE-9380 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Priority: Critical Fix For: 3.3.0.M3 {code} Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 14.995 sec <<< FAILURE! testAlternativesInBeansXml(org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest) Time elapsed: 2.338 sec <<< FAILURE! junit.framework.AssertionFailedError: Marker matches the 'No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]' pattern was found at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertFalse(Assert.java:34) at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:238) at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:232) at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsNotCreated(AbstractResourceMarkerTest.java:393) at org.jboss.tools.cdi.core.test.tck.validation.IncrementalValidationTest.testAlternativesInBeansXml(IncrementalValidationTest.java:129) {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
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9272) Pages from http://download.jboss.org/jbosstools/updates shows folders/files index first and then content of README.htm

by Denis Golovin (JIRA)

Pages from http://download.jboss.org/jbosstools/updates shows folders/files index first and then content of README.htm ---------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9272 URL: https://issues.jboss.org/browse/JBIDE-9272 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Critical Fix For: 3.3.0.M2 Attachments: screenshot76.png After commit *32353 6/24/11 11:19 AM new readmes; remove extraneous index.html pages (or rename to README.html) Links [1] and [2] shows folders/files index first and then content of README.htm Below is an example !screenshot.png! [1] http://download.jboss.org/jbosstools/updates/ [2] http://download.jboss.org/jbosstools/updates/development -- 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-9466) test failures in org.jboss.tools.ws.creation.core.test

by Nick Boldt (JIRA)

test failures in org.jboss.tools.ws.creation.core.test ------------------------------------------------------ Key: JBIDE-9466 URL: https://issues.jboss.org/browse/JBIDE-9466 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing, Webservices Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Fix For: 3.3.0.M4 Attachments: org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt svn co http://svn.jboss.org/repos/jbosstools/trunk/ cd trunk; mvn clean install [INFO] org.jboss.tools.ws.creation.core.test ............. FAILURE [2:15.295s] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9434) JPA: Null text range in HibernateNamedQuery validation process

by Dmitry Geraskov (JIRA)

JPA: Null text range in HibernateNamedQuery validation process -------------------------------------------------------------- Key: JBIDE-9434 URL: https://issues.jboss.org/browse/JBIDE-9434 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M3 java.lang.NullPointerException at org.eclipse.jpt.jpa.core.internal.jpql.JpaJpqlQueryHelper.buildProblem(JpaJpqlQueryHelper.java:135) at org.eclipse.jpt.jpa.core.internal.jpql.JpaJpqlQueryHelper.validate(JpaJpqlQueryHelper.java:232) at org.jboss.tools.hibernate.jpt.core.internal.context.java.HibernateNamedQueryImpl.validateQuery_(HibernateNamedQueryImpl.java:38) at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaQuery.validateQuery(AbstractJavaQuery.java:245) at org.eclipse.jpt.jpa.core.internal.context.java.AbstractJavaQuery.validate(AbstractJavaQuery.java:216) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.validate(AbstractPersistenceUnit.java:2433) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9392) Fix ConsoleConfigurationTest failure

by Dmitry Geraskov (JIRA)

Fix ConsoleConfigurationTest failure ------------------------------------ Key: JBIDE-9392 URL: https://issues.jboss.org/browse/JBIDE-9392 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M3 testHQLListParameters(org.hibernate.eclipse.console.test.ConsoleConfigurationTest) Time elapsed: 0.469 sec <<< ERROR! java.lang.UnsupportedOperationException: The user must supply a JDBC connection at org.hibernate.connection.UserSuppliedConnectionProvider.getConnection(UserSuppliedConnectionProvider.java:54) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1616) at org.hibernate.loader.Loader.doQuery(Loader.java:717) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270) at org.hibernate.loader.Loader.doList(Loader.java:2449) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2192) at org.hibernate.loader.Loader.list(Loader.java:2187) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:452) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.console.HQLQueryPage.getList(HQLQueryPage.java:50) at org.hibernate.eclipse.console.views.QueryPageViewer$ContentProviderImpl.getElements(QueryPageViewer.java:120) at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1010) at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:703) at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1087) at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917) at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1067) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:701) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636) at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690) at org.hibernate.eclipse.console.views.QueryPageViewer.createTable(QueryPageViewer.java:225) at org.hibernate.eclipse.console.views.QueryPageViewer.createControl(QueryPageViewer.java:203) at org.hibernate.eclipse.console.views.QueryPageViewer.<init>(QueryPageViewer.java:160) at org.hibernate.eclipse.console.views.QueryPageTabView.rebuild(QueryPageTabView.java:109) at org.hibernate.eclipse.console.views.QueryPageTabView$1.contentsChanged(QueryPageTabView.java:75) at org.hibernate.eclipse.console.views.QueryPageTabView$1.intervalAdded(QueryPageTabView.java:85) at javax.swing.AbstractListModel.fireIntervalAdded(AbstractListModel.java:130) at org.hibernate.console.QueryPageModel.add(QueryPageModel.java:67) at org.hibernate.console.KnownConfigurations$1.queryPageCreated(KnownConfigurations.java:88) at org.hibernate.console.ConsoleConfiguration.fireQueryPageCreated(ConsoleConfiguration.java:312) at org.hibernate.console.ConsoleConfiguration.access$4(ConsoleConfiguration.java:310) at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:272) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:72) at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:265) at org.hibernate.eclipse.console.test.ConsoleConfigurationTest.testHQLListParameters(ConsoleConfigurationTest.java:155) -- 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-9578) test failure in org.jboss.tools.jsf.test: Process timeout out after 3600 seconds

by Nick Boldt (JIRA)

test failure in org.jboss.tools.jsf.test: Process timeout out after 3600 seconds -------------------------------------------------------------------------------- Key: JBIDE-9578 URL: https://issues.jboss.org/browse/JBIDE-9578 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.M3 Should this test suite be running so long? -- [INFO] org.jboss.tools.jsf.test .......................... FAILURE [1:00:04.930s] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test (default-test) on project org.jboss.tools.jsf.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test (default-test) on project org.jboss.tools.jsf.test: Error while executing platform at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error while executing platform at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:542) at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo.java:348) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.eclipse.tycho.equinox.launching.EquinoxLaunchingException: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. at org.eclipse.tycho.equinox.launching.internal.DefaultEquinoxLauncher.execute(DefaultEquinoxLauncher.java:70) at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo.java:540) ... 22 more Caused by: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:225) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:114) at org.eclipse.tycho.equinox.launching.internal.DefaultEquinoxLauncher.execute(DefaultEquinoxLauncher.java:68) ... 23 more Caused by: java.lang.InterruptedException: Process timeout out after 3600 seconds at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:186) ... 25 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :org.jboss.tools.jsf.test https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/847/con... ---- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
5
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