[
https://issues.jboss.org/browse/WELDRAD-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580090#comment-12580090
]
Dan Allen commented on WELDRAD-26:
----------------------------------
We have the same pain when using Arquillian elsewhere, so this is really an
Arquillian issue (which is really an JBoss AS dependency issue). We are working
to get a consolidated JBoss AS client JAR published that Arquillian can use to
communicate with the remote server.
I absolutely agree that it's ridiculous to download the internet just to deploy
something to the server.
> Reduce/Fix the dependencies of Arquillian test goal in jboss-javaee6-webapp
> archetype
> --------------------------------------------------------------------------------------
>
> Key: WELDRAD-26
> URL: https://issues.jboss.org/browse/WELDRAD-26
> Project: Weld Archetypes
> Issue Type: Feature Request
> Components: javaee6-webapp
> Affects Versions: 1.0.0.Beta2
> Environment: using m2eclipse 0.10 pointing to a standalone maven
> 3.0.2 installation on windows
> Reporter: Robbert van Waveren
>
> There are two special dependencies required for the Arquallian test goal on
> JBoss:
> arquillian-jbossas-remote-6
> jboss-as-client
> this triggers an almost endless download of other dependencies among which
> (as far as I can tell):
> big parts of the jboss AS 6 server
> big parts of the jboss AS 5 server
> (about 300 or so, many of which are the same but with different version
> numbers, taking multiple hours)
> As there are two dependencies I can't say for sure which of the two is
> responsible for the huge dependency tree.
> I suggest some sort of (optional) feature to shortcut this, perhaps with a
> "system" dependency pointing to a local jboss installation client directory.
> finally this results in the following missing dependencies which are not
> available in the new JBoss nexus server using by the generated POM.
> apache-xerces:xml-apis:jar:2.9.1
> javax.security:jacc:jar:1.0
> com.sun.istack:istack-commons-runtime:jar:1.1-SNAPSHOT
> apache-xerces:xml-apis:jar:2.9.1
> and many warnings regarding missing POMs.
> NOTE: adding the deprecated jboss repo as proxy to my companies local nexus
> did fix the missing xerces and xml-apis, however istack-commons-runtime still
> fails.
> As far as I know the archetype is meant to work by default using just the new
> jboss nexus repo, however it currently does not work for me.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
