[JBoss JIRA] (JBIDE-14507) arquillian excessive dependencies includes jsf, seam, project examples and portlets
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14507?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14507:
---------------------------------------
Arquillian doesn't require portlet, jsf or seam, but requires the project.examples plugin that requires these plugins.I will try to exclude the project.examples dependency.
> arquillian excessive dependencies includes jsf, seam,project examples and portlets
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-14507
> URL: https://issues.jboss.org/browse/JBIDE-14507
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Affects Versions: 4.1.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> When [~aslak] installed arquillian he noticed an excessively long list of dependencies:
> Warning: You are installing software that contains unsigned content. The authenticity or validity of this software cannot be established. Do you want to continue with the installation?
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.core_3.4.100.Alpha2-v20130424-2035-B57
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.ui_3.4.100.Alpha2-v20130424-2035-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.archives.webtools_2.4.100.Alpha2-v20130424-2035-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.as.classpath.core_2.4.100.Alpha2-v20130424-2035-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.ide.eclipse.as.ui_2.4.100.Alpha2-v20130424-2035-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.arquillian.core_1.0.4.Beta1-v20130516-1548-B9.jar
> /home/aslak/dev/tools/eclipse-4.3/features/org.jboss.tools.arquillian.feature_1.0.4.Beta1-v20130516-1548-B9
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.arquillian.ui_1.0.4.Beta1-v20130516-1548-B9.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.el.core_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.el.ui_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.model_3.5.0.Alpha2-v20130415-2228-B57
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.model.ui_3.5.0.Alpha2-v20130415-2228-B57
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.projecttemplates_3.5.0.Alpha2-v20130415-2228-B57
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.resref.core_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.text.ext_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.text.xml_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.ui_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.common.validation_3.5.0.Alpha2-v20130415-2228-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jmx.core_1.4.0.Alpha2-v20130424-2035-B57.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jsf_3.5.0.Alpha2-v20130420-0455-B56.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.jsp_3.5.0.Alpha2-v20130420-0309-B33.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.web_3.5.0.Alpha2-v20130420-0309-B33.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.jst.web.kb_3.5.0.Alpha2-v20130420-0309-B33
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.portlet.core_1.5.0.Alpha2-v20130405-1819-B10.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.project.examples_1.5.0.Alpha2-v20130419-1334-B34.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.core_3.5.0.Alpha2-v20130420-0455-B56.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.pages.xml_3.5.0.Alpha2-v20130420-0455-B56.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.seam.xml_3.5.0.Alpha2-v20130420-0455-B56.jar
> /home/aslak/dev/tools/eclipse-4.3/plugins/org.jboss.tools.usage_1.2.0.Alpha2-v20130415-2228-B57.jar
> Why is seam, portlet, jsf and others required ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-14430) Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14430?page=com.atlassian.jira.plugi... ]
Snjezana Peco edited comment on JBIDE-14430 at 5/24/13 5:02 PM:
----------------------------------------------------------------
Currently, Arquillian Eclipse detects the DeploymentContainer implementation(s) by scanning a classpath. It reports an error/a warning if there isn't any or there is more than one implementation.
I propose to solve the issue in the following way:
- scan a classpath
- if there is no implementation of the DeploymentContainer interface, it reports an error
- if there is exactly one implementation of this interface, nothing reported (the Arquillian environment is valid)
- if there is more than one implementation of this interface, we would check if there is the META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension resource on the classpath as well as if there is a class defined in this resource.
If both exist, nothing is reported
Otherwise, Arquillian Eclipse reports an error
I am not sure if it is possible to check if the MyLoadableExtensionClass class activates the DeploymentContainer interface correctly. Maybe we could analyze the b.service(DeplyableContainer.class, MyDeplyableContainer.class) method, check if the MyDeplyableContainer.class exists and implements the DeplyableContainer interface.
was (Author: snjeza):
Currently, Arquillian Eclipse detects the DeploymentContainer implementation(s) by scanning a classpath. It reports an error/a warning if there isn't any or there is more than one implementation.
I propose to solve the issue in the following way:
- scan a classpath
- if there is no implementation of the DeploymentContainer interface, it reports an error
- if there is exactly one implementation of this interface, nothing reported (the Arquillian environment is valid)
- if there is more than one implementation of this interface, we would check if there is the META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension resource on the classpath as well as if there is a class defined in this resource.
If both exist, nothing is reported
Otherwise, Arquillian Eclipse reports an error
I am not sure if it is possible to check if the MyLoadableExtensionClass class activates the Deplo ymentContainer interface correctly. Maybe we could analyze the b.service(DeplyableContainer.class, MyDeplyableContainer.class) method, check if the MyDeplyableContainer.class exists and implements the DeplyableContainer interface.
> Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14430
> URL: https://issues.jboss.org/browse/JBIDE-14430
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> can't we detect if there is more than one DeploymentContainer for Run As > Arquillian test or is that too slow ?
> Or at least show which profile is enabled or something to give user an idea what he is currently running with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-14624) Seam 2 project deployed to EAP 5.1 is not running
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14624?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-14624:
---------------------------------------
Reported to bugzilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=409036
> Seam 2 project deployed to EAP 5.1 is not running
> -------------------------------------------------
>
> Key: JBIDE-14624
> URL: https://issues.jboss.org/browse/JBIDE-14624
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam 2, upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206
> JBoss EAP 5.1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
>
> 1. Generate seam project for EAP5.1 runtime and Seam included in this EAP
> 2. Run it on EAP5.1 server
> ERROR:
> {noformat}
> 11:43:14,215 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/ state=PreParse mode=Manual requiredState=Parse
> org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/opt/jboss-eap-5.1/jboss-as/server/default/deploy/seam5170.war/
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
> at org.jboss.Main.boot(Main.java:221)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
> at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
> at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
> at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)
> at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
> ... 33 more
> Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element.
> at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
> at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
> ... 42 more
> {noformat}
> Looks like incorrect namespaces are used in web.xml file:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:web="http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
> When web.xml file is opened in editor via double click it's not opened in web.xml editor. It has only source displayed. There is no Tree tab.
> When replaced with definition from web.xml file generated by JBDS 6.0.0 Everything works as expected:
> {noformat}
> <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" id="WebApp_ID" version="2.5">
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-14430) Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14430?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14430:
---------------------------------------
Currently, Arquillian Eclipse detects the DeploymentContainer implementation(s) by scanning a classpath. It reports an error/a warning if there isn't any or there is more than one implementation.
I propose to solve the issue in the following way:
- scan a classpath
- if there is no implementation of the DeploymentContainer interface, it reports an error
- if there is exactly one implementation of this interface, nothing reported (the Arquillian environment is valid)
- if there is more than one implementation of this interface, we would check if there is the META-INF/services/org.jboss.arquillian.core.spi.LoadableExtension resource on the classpath as well as if there is a class defined in this resource.
If both exist, nothing is reported
Otherwise, Arquillian Eclipse reports an error
I am not sure if it is possible to check if the MyLoadableExtensionClass class activates the Deplo ymentContainer interface correctly. Maybe we could analyze the b.service(DeplyableContainer.class, MyDeplyableContainer.class) method, check if the MyDeplyableContainer.class exists and implements the DeplyableContainer interface.
> Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14430
> URL: https://issues.jboss.org/browse/JBIDE-14430
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: testing-tools
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> can't we detect if there is more than one DeploymentContainer for Run As > Arquillian test or is that too slow ?
> Or at least show which profile is enabled or something to give user an idea what he is currently running with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years