[JBoss JIRA] Created: (ARQ-290) performence/pom.xml references WELD-1.0.1
by steven verborgh (JIRA)
performence/pom.xml references WELD-1.0.1
-----------------------------------------
Key: ARQ-290
URL: https://jira.jboss.org/browse/ARQ-290
Project: Arquillian
Issue Type: Bug
Components: Build Infrastructure
Environment: Mac OS, Maven 3, using jboss-repository-public as in JBoss maven Getting started wiki
Reporter: steven verborgh
build fails with:
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR] The project org.jboss.arquillian.extension:arquillian-performance:1.0.0-SNAPSHOT (/Users/verborghs/Documents/Repositories/arquilian/arquillian/arquillian/extensions/performance/pom.xml) has 4 errors
[ERROR] Non-resolvable import POM org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT: Failed to resolve POM for org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT due to The following artifacts could not be resolved: org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT: Could not find artifact org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=true, managed=false) @ line 105, column 26 -> [Help 2]
[ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-core:jar is missing. @ line 84, column 25
[ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-api:jar is missing. @ line 88, column 25
[ERROR] 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ line 92, column 25
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Solved by replacing 1.0.2-SNAPSHOT which is no longer in https://repository.jboss.org/nexus/content/groups/public-jboss/ to 1.1.0-SNAPSHOT
--
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
13 years, 10 months
[JBoss JIRA] Created: (ARQ-171) ServletMethodExecutor should get context path from container
by Dan Allen (JIRA)
ServletMethodExecutor should get context path from container
------------------------------------------------------------
Key: ARQ-171
URL: https://jira.jboss.org/browse/ARQ-171
Project: Arquillian
Issue Type: Bug
Components: Test Protocol SPIs and Implementation
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
While working on the JSR 88 container implementation, I noticed that ServletMethodExecutor is using the hard-coded context path "/test" to communicate with the application to invoke the ArquillianServletRunner. I think that the context path is something that the container implementation should be passing to the ServletMethodExecutor in the deploy() method.
This assumption poses a particular problem in the JSR 88 container. When a WAR is deployed using JSR 88, the module is assigned a random name, and hence a random context path. Since there is no way to override the context path "/test" used by the ServletMethodExecutor, it fails to communicate with the server.
The ServletMethodExecutor constructor should be changed to take the context path as the second parameter. All the container implementations will need to be updated accordingly.
--
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
13 years, 10 months