[JBoss JIRA] (JBIDE-10663) Cannot start JBossAS 7.1.0
by Juergen Zimmermann (JIRA)
Juergen Zimmermann created JBIDE-10663:
------------------------------------------
Summary: Cannot start JBossAS 7.1.0
Key: JBIDE-10663
URL: https://issues.jboss.org/browse/JBIDE-10663
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
I just tried the latest Jenkins build 2349 for the upcoming 7.1.0.Final. When I try to start the JBoss server I'm getting the error message "Invalid option '-logmodule'" in the console.
When I remove "-logmodule org.jboss.logmanager" from the "Program arguments" within the launch configuration, then the server is starting fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10688) EAP 6 DR11 not recognized properly when added
by Martin Malina (JIRA)
Martin Malina created JBIDE-10688:
-------------------------------------
Summary: EAP 6 DR11 not recognized properly when added
Key: JBIDE-10688
URL: https://issues.jboss.org/browse/JBIDE-10688
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Environment: JBoss Tools Nightly - 3.3.0.v20120118-1032-H4144-Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
When you try to add EAP 6.0.0 DR11 as a server in JBT it will display a warning:
This server type expects a version of 6. but the server directory is of version 7.1.0.CR1-redhat-1.
The same happens with DR12, but not DR8. I don't know where exactly JBT is looking for the version number within the AS directory (I was able to find 7.1.0.CR1-redhat-1 in many modules' config) but it seems the older DR releases probably showed version 6, but now they are derived from the JBoss AS version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10638) InvocationTargetException while importing Java EE Project from Central
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-10638:
--------------------------------------
Summary: InvocationTargetException while importing Java EE Project from Central
Key: JBIDE-10638
URL: https://issues.jboss.org/browse/JBIDE-10638
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, project-examples
Affects Versions: 3.3.0.Beta1
Reporter: Alexey Kazakov
Assignee: Snjezana Peco
I'm not sure if it's an issue with the example or maven integration or maybe it's just a bug of WTP.
Here is the exception thath I get:
{code}
java.lang.reflect.InvocationTargetException
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$2.run(ArchetypeExamplesWizard.java:122)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.wst.common.project.facet.core.FacetedProjectFrameworkException: Failed while installing JavaServer Faces 2.0.
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1507)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.installJSFFacet(JSFProjectConfigurator.java:229)
at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.installWarFacets(JSFProjectConfigurator.java:186)
at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configureInternal(JSFProjectConfigurator.java:138)
at org.jboss.tools.maven.jsf.configurators.JSFProjectConfigurator.configure(JSFProjectConfigurator.java:114)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:303)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:242)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:152)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:581)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$1.run(ArchetypeExamplesWizard.java:108)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$2.run(ArchetypeExamplesWizard.java:120)
... 1 more
Caused by: java.lang.RuntimeException: org.osgi.service.prefs.BackingStoreException: Resource '/multi/multi-web/.settings' does not exist.
at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:224)
at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.execute(LibraryInstallDelegate.java:597)
at org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:116)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
... 20 more
Caused by: org.osgi.service.prefs.BackingStoreException: Resource '/multi/multi-web/.settings' does not exist.
at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:174)
at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferences.flush(ProjectFacetPreferences.java:412)
at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProviderFrameworkImpl.setCurrentProvider(LibraryProviderFrameworkImpl.java:220)
... 23 more
Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/multi/multi-web/.settings' does not exist.
at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:320)
at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:194)
at org.eclipse.core.internal.resources.File.create(File.java:114)
at org.eclipse.core.internal.resources.File.create(File.java:187)
at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:358)
at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:321)
at org.eclipse.wst.common.project.facet.core.util.internal.FileUtil.writeFile(FileUtil.java:307)
at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetPreferencesGroup.save(ProjectFacetPreferencesGroup.java:165)
... 25 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10614) org.jboss.ide.eclipse.as.management.as7.tests currently fails
by Andre Dietisheim (Created) (JIRA)
org.jboss.ide.eclipse.as.management.as7.tests currently fails
-------------------------------------------------------------
Key: JBIDE-10614
URL: https://issues.jboss.org/browse/JBIDE-10614
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.Beta1
Currently the as7 management service test (not the integration tests) is failing:
*JBossManagementServiceTest#serviceIsReachable* spits the following:
{code}
java.lang.AssertionError: org.jboss.ide.eclipse.as.management.as7 not installed
at org.junit.Assert.fail(Assert.java:91)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertNotNull(Assert.java:524)
at org.jboss.ide.eclipse.as.internal.management.as7.tests.JBossManagementServiceTest.ensureServiceBundleIsRunning(JBossManagementServiceTest.java:59)
at org.jboss.ide.eclipse.as.internal.management.as7.tests.JBossManagementServiceTest.serviceIsReachable(JBossManagementServiceTest.java:46)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62)
at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23)
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.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10583) ClassCastException while CDIProject.getBeans() is working
by Daniel Azarov (Created) (JIRA)
ClassCastException while CDIProject.getBeans() is working
---------------------------------------------------------
Key: JBIDE-10583
URL: https://issues.jboss.org/browse/JBIDE-10583
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.M5
Reporter: Daniel Azarov
Assignee: Alexey Kazakov
EXECUTE: Create two CDI projects: ProjectA and ProjectB. ProjectB depends on ProjectA.
EXECUTE: Create a bean in ProjectA:
{code}
@Named("cdiBean")
public class CDIBeanTest {
}
{code}
EXECUTE: Create another bean in ProjectB:
{code}
public class TestBean {
@Inject @Named("cdiBean") Object foo;
}
{code}
EXECUTE: Close ProjectB
EXECUTE: Select CDIBeanTest class name in CDIBeanTest.java and press Ctrl+Shift+G
Two results were found:
1. Exception:
{code}
java.lang.ClassCastException: org.eclipse.jdt.internal.compiler.classfmt.AnnotationInfo cannot be cast to org.eclipse.jdt.internal.core.SourceRefElementInfo
at org.eclipse.jdt.internal.core.SourceRefElement.getSourceRange(SourceRefElement.java:218)
at org.eclipse.jdt.internal.core.Annotation.getSourceRange(Annotation.java:121)
at org.jboss.tools.common.java.impl.JavaAnnotation.getStartPosition(JavaAnnotation.java:68)
at org.jboss.tools.common.java.impl.AnnotationDeclaration.getStartPosition(AnnotationDeclaration.java:84)
at org.jboss.tools.cdi.internal.core.impl.AbstractBeanElement.getRestrictedTypeDeclarations(AbstractBeanElement.java:292)
at org.jboss.tools.cdi.internal.core.impl.ClassBean.getLegalTypes(ClassBean.java:348)
at org.jboss.tools.cdi.internal.core.impl.CDIProject.getBeans(CDIProject.java:372)
at org.jboss.tools.cdi.ui.search.CDIBeanQueryParticipant.searchInProject(CDIBeanQueryParticipant.java:96)
at org.jboss.tools.cdi.ui.search.CDIBeanQueryParticipant.search(CDIBeanQueryParticipant.java:73)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery$2.run(JavaSearchQuery.java:164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:170)
at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
2. TestBean.foo is found as an injection point and can be opened in external editor
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-8394) Fetching inaccesible db can cause irresponsive ui and other issues
by Jiri Peterka (JIRA)
Fetching inaccesible db can cause irresponsive ui and other issues
------------------------------------------------------------------
Key: JBIDE-8394
URL: https://issues.jboss.org/browse/JBIDE-8394
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.2.0.CR2 (tentative)
Environment: JBDS 4.0.0.CR3 H162, Linux 64
Reporter: Jiri Peterka
Priority: Critical
UI is not responsive when trying to connect stopped DB, some independent actions (like connection other running databases is blocked as well). When rebuild configuration is trigged, ui is completely frozen. Screencast http://www.screencast.com/t/p9uP59dNt
Expected state:
1. Connection try should be shorter
2. Stopping fetching job should work
3. Independent databases should be always accesssible
4. IDE should not be freezing or forbidden action should be disabled
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month