[jbosstools-issues] [JBoss JIRA] (JBIDE-16701) Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final
Aslak Knutsen (JIRA)
issues at jboss.org
Fri Jan 30 14:24:49 EST 2015
[ https://issues.jboss.org/browse/JBIDE-16701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036565#comment-13036565 ]
Aslak Knutsen commented on JBIDE-16701:
---------------------------------------
[~fbricon] Technically you can run them as long as they're EE6 apps.. But it would require a different Container adapter as WildFly is diverging more and more from EAP.
> Arquillian not working with default maven settings from selecting the jboss-javaee6-webapp-archetype 7.1.3.Final
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16701
> URL: https://issues.jboss.org/browse/JBIDE-16701
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, maven
> Affects Versions: 4.1.1.Final
> Reporter: Dirk Gerrit Oort
> Fix For: 4.2.x
>
>
> (see https://community.jboss.org/message/860583#860583)
> Create maven project with archetype selecting the jboss-javaee6-webapp-archetype 7.1.3.Final
> use arq-jbossas-managed
> use jboss 7.1.1
> run maven test
> deployment is done but after deployment the test 'hangs'
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list