[JBoss JIRA] (JBIDE-17596) Cannot run test on WELD EE 1.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17596?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17596:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> Cannot run test on WELD EE 1.1
> ------------------------------
>
> Key: JBIDE-17596
> URL: https://issues.jboss.org/browse/JBIDE-17596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools, upstream
> Affects Versions: 4.2.0.Beta2
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
>
> When I try to run simple test with WELD 1.1 maven profile the test fails with the following exception:
> {code}
> java.lang.NoClassDefFoundError: javax/ejb/Stateless
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.findEjbs(Ejbs.java:38)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.createEjbDescriptors(Ejbs.java:25)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:81)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.<init>(TestContainer.java:228)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:99)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
> 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:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> 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:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: java.lang.ClassNotFoundException: javax.ejb.Stateless
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 92 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18383) forge command rely on english description label to lookup commands - fragile!
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18383?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18383:
----------------------------------------
Assignee: Koen Aers (was: George Gastaldi)
> forge command rely on english description label to lookup commands - fragile!
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18383
> URL: https://issues.jboss.org/browse/JBIDE-18383
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> it seems this is the way forge commands are looked up:
> org.jboss.tools.forge.ui.runForgeCommand(org.jboss.tools.forge.ui.runForgeCommand.commandName=REST: Generate Endpoints From Entities)"
> meaning if description changes the cheatsheet breaks.
> should this not us a unique id or at least the cli command name so we have *one* API to obey to ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-17940) JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17940?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17940:
----------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.CR2)
> JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17940
> URL: https://issues.jboss.org/browse/JBIDE-17940
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3, GNU/Linux 64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.1.Final
>
>
> JPA Details view is not working for entities in autodiscovery mode. It only works when entities are added into Managed Classes entities list. It's expected when JPA project is configured with "Discover annotated classes automatically" it should without manual listing entities in persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-16502) FrameworkEvent ERROR after JBT installation (tracker for upstream issue)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16502?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16502:
----------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.CR2)
> FrameworkEvent ERROR after JBT installation (tracker for upstream issue)
> ------------------------------------------------------------------------
>
> Key: JBIDE-16502
> URL: https://issues.jboss.org/browse/JBIDE-16502
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Alpha2
> Environment: JBT 4.2.0.Alpha2, L64, Fedora 19, OpenJDK 1.7
> Reporter: Jiri Peterka
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.2.1.Final
>
>
> After Eclipse Luna M5 JEE + JBT 4.2.0.Alpha2 installation there is:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.jpt.dbws.eclipselink.ui [388]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.eclipse.osgi.container.Module.start(Module.java:424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Caused by: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> ... 7 more
> Root exception:
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"] because it is exposed to package 'javax.xml.bind' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"] and javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"] via two dependency chains.
> Chain 1:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.wst.common.project.facet.ui)(&(bundle-version>=1.3.0)(!(bundle-version>=2.0.0))))
> |
> provide: osgi.wiring.bundle: org.eclipse.wst.common.project.facet.ui
> org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.0.v20140121-0337"; singleton:="true"]
> Chain 2:
> org.eclipse.jpt.dbws.eclipselink.ui [osgi.identity; osgi.identity="org.eclipse.jpt.dbws.eclipselink.ui"; type="osgi.bundle"; version:Version="1.1.100.v201310142259"; singleton:="true"]
> require: (&(osgi.wiring.bundle=org.eclipse.persistence.dbws.builder)(&(bundle-version>=2.3.0)(!(bundle-version>=3.0.0))))
> |
> provide: osgi.wiring.bundle; osgi.wiring.bundle="org.eclipse.persistence.dbws.builder"; bundle-version:Version="2.6.0.v20130815-a4708b6"
> org.eclipse.persistence.dbws.builder [osgi.identity; osgi.identity="org.eclipse.persistence.dbws.builder"; type="osgi.bundle"; version:Version="2.6.0.v20130815-a4708b6"]
> import: (osgi.wiring.package=javax.xml.bind)
> |
> export: osgi.wiring.package: javax.xml.bind
> javax.xml.bind [osgi.identity; osgi.identity="javax.xml.bind"; type="osgi.bundle"; version:Version="2.1.9.v201005080401"]
> at org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1286)
> at org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1078)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:249)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18368) An internal error occurred during: "Computing connector status".
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18368?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18368:
----------------------------------------
I've tried to understand why this agent can be null at that time and couldn't figure out. I'll just put a null-check guard...
> An internal error occurred during: "Computing connector status".
> ----------------------------------------------------------------
>
> Key: JBIDE-18368
> URL: https://issues.jboss.org/browse/JBIDE-18368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.CR1b, F20_64
> Reporter: Jiri Peterka
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR2
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveProfileUnits(ConnectorDescriptorItemUi.java:393)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$6(ConnectorDescriptorItemUi.java:390)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:311)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18235) Improve publication of *-earlyaccess.properties files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18235?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-18235.
----------------------------------
Resolution: Rejected
We already have discovery jobs publishing the *-earlyaccess.properties files automatically to nightly directory whenever a change is noticed on repository.
We don't need to do it again in promote.sh.
> Improve publication of *-earlyaccess.properties files
> -----------------------------------------------------
>
> Key: JBIDE-18235
> URL: https://issues.jboss.org/browse/JBIDE-18235
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, discovery
> Affects Versions: 4.2.0.CR1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.0.Final
>
>
> Currently, there are explicit steps in discovery job configurations (cf JBIDE-18228) to publish the *-earlyaccess.properties file to nightly directories.
> Instead, we should consider making publication more standard and rely on promote.sh.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-16066:
-------------------------------------------
Hey Rob - as to the JBDS 8 issue. I'm seeing the 'Refreshing Process Information' NPE that I believe has already been solved for CR2 (An internal error occurred during: "Refreshing Process Information" : java.lang.NullPointerException)
{code}
java.lang.NullPointerException
at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:96)
at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:66)
at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
{code}
eclipse.buildId=unknown
java.version=1.7.0_67
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
Command-line arguments: -os win32 -ws win32 -arch x86 -application org.eclipse.ui.ide.workbench -product com.jboss.devstudio.core.product
{code}
In the console, it freezes:
{code}
06:54:00,492 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
06:54:02,972 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
06:54:03,347 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
{code}
Status messages seem to show "Starting JBoss Enterprise Application Platform 6.1+... Preparing launch delegate..." and it's pegged at 100%. I'm not seeing anything else in the Error Log beyond the earlier NPE.
Nothing appears in the server.log or boot.log since last night (just tried to restart again in JBDS 8 and it just sticks).
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.CR2
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18235) Improve publication of *-earlyaccess.properties files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18235?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-18235:
-----------------------------------
Fix Version/s: 4.2.0.Final
(was: 4.2.0.CR2)
> Improve publication of *-earlyaccess.properties files
> -----------------------------------------------------
>
> Key: JBIDE-18235
> URL: https://issues.jboss.org/browse/JBIDE-18235
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, discovery
> Affects Versions: 4.2.0.CR1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.0.Final
>
>
> Currently, there are explicit steps in discovery job configurations (cf JBIDE-18228) to publish the *-earlyaccess.properties file to nightly directories.
> Instead, we should consider making publication more standard and rely on promote.sh.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months