[JBoss JIRA] Commented: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails
by Max Rydahl Andersen (JIRA)
[ https://jira.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen commented on JBIDE-6464:
--------------------------------------------
Moved from seam to jbide since it is related to the eclipse tooling on the first sight.
Shu-Wei Tan, could you let us know which specific versions of JBoss Tools and Seam you are using ?
> Running a SeamTest when multiple projects are open in the Eclipse workspace fails
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-6464
> URL: https://jira.jboss.org/browse/JBIDE-6464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam
> Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA
> Reporter: Shu-Wei Tan
>
> My eclipse workspace contains 2 JBoss Tools generated Seam projects:
> - Project1.war
> - Project1.ear
> - Project1.ejb
> - Project1.test
> - Project2.war
> - Project2.ear
> - Project2.ejb
> - Project2.test
> Project2.ear depends on both Project1.ejb and Project2.ejb.
> Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear.
> If I close the Project1.ear project in Eclipse then rerun the test, it works.
> Here's the exception (the actual project name is different from my simplified example above):
> ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
> at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127)
> at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289)
> at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19)
> at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024)
> at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915)
> at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284)
> at org.testng.SuiteRunner.run(SuiteRunner.java:204)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:842)
> at org.testng.TestNG.run(TestNG.java:751)
> at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
> at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124)
> Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486)
> at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468)
> at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434)
> at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145)
> ... 36 more
> Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536)
> ... 41 more
--
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, 10 months
[JBoss JIRA] Moved: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails
by Max Rydahl Andersen (JIRA)
[ https://jira.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin.s... ]
Max Rydahl Andersen moved JBSEAM-4656 to JBIDE-6464:
----------------------------------------------------
Project: Tools (JBoss Tools) (was: Seam)
Key: JBIDE-6464 (was: JBSEAM-4656)
Affects Version/s: (was: 2.2.0.GA)
Component/s: Seam
(was: Test Harness)
> Running a SeamTest when multiple projects are open in the Eclipse workspace fails
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-6464
> URL: https://jira.jboss.org/browse/JBIDE-6464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam
> Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA
> Reporter: Shu-Wei Tan
>
> My eclipse workspace contains 2 JBoss Tools generated Seam projects:
> - Project1.war
> - Project1.ear
> - Project1.ejb
> - Project1.test
> - Project2.war
> - Project2.ear
> - Project2.ejb
> - Project2.test
> Project2.ear depends on both Project1.ejb and Project2.ejb.
> Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear.
> If I close the Project1.ear project in Eclipse then rerun the test, it works.
> Here's the exception (the actual project name is different from my simplified example above):
> ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
> at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127)
> at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289)
> at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19)
> at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024)
> at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915)
> at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284)
> at org.testng.SuiteRunner.run(SuiteRunner.java:204)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:842)
> at org.testng.TestNG.run(TestNG.java:751)
> at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
> at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124)
> Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486)
> at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468)
> at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434)
> at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145)
> ... 36 more
> Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536)
> ... 41 more
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6428) compilation failure in WS component due to access restrictions on org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
by Nick Boldt (JIRA)
compilation failure in WS component due to access restrictions on org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-6428
URL: https://jira.jboss.org/browse/JBIDE-6428
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Nick Boldt
Assignee: Brian Fitzpatrick
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-3.2.0.M1/...
Compilation failure:
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/views/WSDLBrowseDialog.java (at line 30):[-1,-1]
import javax.wsdl.extensions.soap12.SOAP12Binding;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Binding is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/views/WSDLBrowseDialog.java (at line 410):[-1,-1]
if (elements.get(i) instanceof SOAPBinding || elements.get(i) instanceof SOAP12Binding ) {
^^^^^^^^^^^^^
Access restriction: The type SOAP12Binding is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 42):[-1,-1]
import javax.wsdl.extensions.soap12.SOAP12Address;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Address is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 43):[-1,-1]
import javax.wsdl.extensions.soap12.SOAP12Operation;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Operation is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 182):[-1,-1]
} else if (element instanceof SOAP12Address) {
^^^^^^^^^^^^^
Access restriction: The type SOAP12Address is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 183):[-1,-1]
SOAP12Address address = (SOAP12Address) element;
^^^^^^^^^^^^^
Access restriction: The type SOAP12Address is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 183):[-1,-1]
SOAP12Address address = (SOAP12Address) element;
^^^^^^^^^^^^^
Access restriction: The type SOAP12Address is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 184):[-1,-1]
return address.getLocationURI();
^^^^^^^^^^^^^^^^^^^^^^^^
Access restriction: The method getLocationURI() from the type SOAP12Address is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 218):[-1,-1]
} else if (test instanceof SOAP12Operation) {
^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Operation is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 219):[-1,-1]
SOAP12Operation soapOp = (SOAP12Operation) test;
^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Operation is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 219):[-1,-1]
SOAP12Operation soapOp = (SOAP12Operation) test;
^^^^^^^^^^^^^^^
Access restriction: The type SOAP12Operation is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
/mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.ui/src/org/jboss/tools/ws/ui/utils/TesterWSDLUtils.java (at line 220):[-1,-1]
return soapOp.getSoapActionURI();
^^^^^^^^^^^^^^^^^^^^^^^^^
Access restriction: The method getSoapActionURI() from the type SOAP12Operation is not accessible due to restriction on classpath entry /mnt/hudson_workspace/workspace/jbosstools-3.2.0.M1/sources/ws/plugins/org.jboss.tools.ws.creation.core/lib/wsdl4j.jar
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6444) Switch Helios build to use new b3 aggregator instead of bucky aggregator to resolve install dep issues
by Nick Boldt (JIRA)
Switch Helios build to use new b3 aggregator instead of bucky aggregator to resolve install dep issues
------------------------------------------------------------------------------------------------------
Key: JBIDE-6444
URL: https://jira.jboss.org/browse/JBIDE-6444
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.2-Helios
Because bucky aggregator depends explicitly on 3.5 (not 3.5+) we can no longer use it for a Helios based build. Console log:
> prefetchRepoZips:
> [get] Getting:
> http://repository.jboss.org/eclipse/galileo/repos/buckminster-updates-3.5...
>
> [get] To:
> /home/eskimo/Projects/jbds-build-helios/requirements/p2repos/buckminster-updates-3.5_20100125-r11098.zip
>
> [taskdef] Could not load definitions from resource
> net/sf/antcontrib/antlib.xml. It could not be found.
>
> prefetchRepoZips:
> [p2.dir] Installing
> org.eclipse.buckminster.aggregator.engine.feature.feature.group
> 1.0.0.r11097.
> [p2.dir] Installation failed.
> [p2.dir] Cannot complete the install because of a conflicting dependency.
> [p2.dir] Software being installed: Buckminster Aggregator Engine
> 1.0.0.r11097
> (org.eclipse.buckminster.aggregator.engine.feature.feature.group
> 1.0.0.r11097)
> [p2.dir] Software currently installed: Eclipse SDK 3.6.0.I20100520-1744
> (org.eclipse.sdk.ide 3.6.0.I20100520-1744)
> [p2.dir] Only one of the following can be installed at once:
> [p2.dir] Equinox Provisioning Core 1.0.101.R35x_v20090819
> (org.eclipse.equinox.p2.core 1.0.101.R35x_v20090819)
> [p2.dir] Equinox Provisioning Core 1.0.100.v20090520-1905
> (org.eclipse.equinox.p2.core 1.0.100.v20090520-1905)
> [p2.dir] Equinox Provisioning Core 2.0.0.v20100510
> (org.eclipse.equinox.p2.core 2.0.0.v20100510)
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Buckminster Aggregator Model 1.0.0.r11090
> (org.eclipse.buckminster.aggregator 1.0.0.r11090)
> [p2.dir] To: package org.eclipse.equinox.internal.provisional.p2.query
> 0.0.0
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Buckminster Aggregator Engine 1.0.0.r11097
> (org.eclipse.buckminster.aggregator.engine.feature.feature.group
> 1.0.0.r11097)
> [p2.dir] To: org.eclipse.buckminster.aggregator [1.0.0,1.1.0)
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Equinox p2 Provisioning
> 2.0.0.v20100503-897HFZ-FdHjO1VQjpcrvF5J
> (org.eclipse.equinox.p2.user.ui.feature.group
> 2.0.0.v20100503-897HFZ-FdHjO1VQjpcrvF5J)
> [p2.dir] To: org.eclipse.equinox.p2.core [2.0.0.v20100510]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse SDK 3.6.0.I20100520-1744 (org.eclipse.sdk.ide
> 3.6.0.I20100520-1744)
> [p2.dir] To: org.eclipse.equinox.p2.user.ui.feature.group
> [2.0.0.v20100503-897HFZ-FdHjO1VQjpcrvF5J]
> [p2.dir] Application failed, log file location:
> /home/eskimo/Projects/jbds-build-helios/jbds-build/clean-eclipse/eclipse/configuration/1276071868982.log
>
> [p2.dir] !SESSION 2010-06-09 01:24:28.719
> -----------------------------------------------
> [p2.dir] eclipse.buildId=I20100520-1744
> [p2.dir] java.version=1.6.0_18
> [p2.dir] java.vendor=Sun Microsystems Inc.
> [p2.dir] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> [p2.dir] Framework arguments: -application
> org.eclipse.equinox.p2.director -flavor tooling -roaming -profile
> SDKProfile -installIU
> org.eclipse.buckminster.aggregator.engine.feature.feature.group
> -destination
> /home/eskimo/Projects/jbds-build-helios/jbds-build/clean-eclipse/eclipse
> -bundlepool
> /home/eskimo/Projects/jbds-build-helios/jbds-build/clean-eclipse/eclipse
> -metadataRepository
> jar:file:/home/eskimo/Projects/jbds-build-helios/requirements/p2repos/buc...
> -artifactRepository
> jar:file:/home/eskimo/Projects/jbds-build-helios/requirements/p2repos/buc...
> -profileProperties org.eclipse.update.install.features=true
> [p2.dir] Command-line arguments: -os linux -ws gtk -arch x86
> -application org.eclipse.equinox.p2.director -consoleLog -flavor tooling
> -roaming -profile SDKProfile -installIU
> org.eclipse.buckminster.aggregator.engine.feature.feature.group
> -destination
> /home/eskimo/Projects/jbds-build-helios/jbds-build/clean-eclipse/eclipse
> -bundlepool
> /home/eskimo/Projects/jbds-build-helios/jbds-build/clean-eclipse/eclipse
> -metadataRepository
> jar:file:/home/eskimo/Projects/jbds-build-helios/requirements/p2repos/buc...
> -artifactRepository
> jar:file:/home/eskimo/Projects/jbds-build-helios/requirements/p2repos/buckminster-updates-3.5_20100125-r11098.zip!/,http://downl
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-4304) Autoconfigure datasources from JBoss in DTP
by Max Rydahl Andersen (JIRA)
Autoconfigure datasources from JBoss in DTP
-------------------------------------------
Key: JBIDE-4304
URL: https://jira.jboss.org/jira/browse/JBIDE-4304
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Max Rydahl Andersen
Fix For: 3.1.0.M1, 3.1.0.M2
It would be great if DTP would automatically (or semi-automatically) could be configured to pickup the -ds.xml in a server runtime so users didn't have to set it up.
Not sure where in the ui we should have this, a couple of options come to my mind:
1) At AS Server/runtime creation have a checkbox saying "Configure -ds.xml automatically in DTP" and then we will keep DTP informed about the -ds.xml files for it to pick up
2) In DTP's ui have a way to add or maybe only import a -ds.xml and have it preconfigured.
The biggest issue will be to know which drivers we should be using for -ds.xml...
Things that should be considered:
If users changes the -ds.xml how does DTP learn about it ?
If the users remove the -ds.xml how does DTP react ?
If the users add .?
Needs investigation into if DTP have extensions point that allows for this kind of 'monitored' resources to update the connections; or if it is better to simply just have a way to "import" settings from ds.xml's (and then possibly have a manual refresh to pickup changes)
Or have both.
The usecase for this is to be able to use already existing and newly added -ds.xml files from within Eclipse with minimal setup, i.e. for Seam and Dali projects.
(I think this is a duplicate, but couldn't find it ;(
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6384) Clean up JstJspAllTests form tests that actuallytests functionality injected by client plugins
by Denis Golovin (JIRA)
Clean up JstJspAllTests form tests that actuallytests functionality injected by client plugins
----------------------------------------------------------------------------------------------
Key: JBIDE-6384
URL: https://jira.jboss.org/browse/JBIDE-6384
Project: Tools (JBoss Tools)
Issue Type: Task
Components: testing
Affects Versions: 3.2.0.M1
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 3.2.0.M1
Example:
JstJspJbide1759Test fails in tycho build because o.j.t.jsf plug-in is not declared as dependency of jst.jsp.tests plug-in.JstJspJbide1759Test tests actually functionality provided by o.j.t.jsf through extension points.
Tests that should be moved down along the hierarchy to jsf, seam or even vpe components are:
suite.addTestSuite(CAForUnclosedELTest.class);
suite.addTestSuite(CAForCompositeComponentTest.class);
suite.addTestSuite(MissingKBBuilderTest.class);
suite.addTestSuite(JsfJspJbide1807Test.class);
suite.addTestSuite(CAForIDTest.class);
suite.addTestSuite(JsfJspJbide1813Test.class);
suite.addTestSuite(JstJspJbide1759Test.class);
suite.addTestSuite(JsfJspJbide2437Test.class);
suite.addTestSuite(JsfJspJbide2016Test.class);
suite.addTestSuite(CAForELinStyleTest.class);
--
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, 10 months