[JBoss JIRA] Created: (ARQ-66) provide a mechanism for adding library JARs (test dependencies) to the deployment
by Dan Allen (JIRA)
provide a mechanism for adding library JARs (test dependencies) to the deployment
---------------------------------------------------------------------------------
Key: ARQ-66
URL: https://jira.jboss.org/jira/browse/ARQ-66
Project: Arquillian
Issue Type: Feature Request
Components: Core
Reporter: Dan Allen
Assignee: Pete Muir
Fix For: 1.0.0-alpha-1
The requirement to add extra JARs into the deployment is going to surface fairly early on in the adoption of Arquillian. In our examples, we are sticking to APIs in Java EE, but most projects have third-party JARs on which the application depends. Common examples are a logging framework, Apache Commons libraries, Google Collections, Hibernate Search...anything not available in the container.
We might need to update the @Deployment signature to support:
@Deployment
static Set<Archive<?>> x();
Or maybe a seperate @DeploymentDependencies (this could be defined in e.g. a super class)
@DeploymentDependencies
static Set<Archive<?>> x()
We are also going to need to consider providing APIs for resolving Maven dependencies (groupId, artifactId, version) or resolving test dependencies from the Maven pom. We need to be flexible.
--
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
13 years, 1 month
[JBoss JIRA] Created: (ARQ-363) Create a separate Arquillian Deployer war for JBoss AS Servers
by Aslak Knutsen (JIRA)
Create a separate Arquillian Deployer war for JBoss AS Servers
--------------------------------------------------------------
Key: ARQ-363
URL: https://issues.jboss.org/browse/ARQ-363
Project: Arquillian
Issue Type: Feature Request
Components: JBoss Containers
Affects Versions: 1.0.0.Beta1
Environment: JBoss AS 4, 5, 6
Reporter: Aslak Knutsen
Fix For: 1.0.0.CR1
The JBoss AS Client lib has a dependency set of 249 libs that blow up on windows machines where classpath length is a issue.
ProfileService Management View only expose parts of the info we need, so to reliably deploy and introspect our deployments we need to create our own little WAR that can do the following:
- Act as a Rest like Deployer / UnDeployer
- this will remove the need for a client api all together
- Hook into the JBoss AS internal deployer chain and extract as much info about the deployment as possible
- servlets - classes, mappings, contexts
- ejbs - classes, interfaces, remote, local, jndi names
- ws - end points etc
The metadata will be used by the Protocols to find where to do the test invocation, client and incontainer @EJB enrichment, Servlet URL enrichment, etc..
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month