[ https://issues.apache.org/jira/browse/DELTASPIKE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael Benevides resolved DELTASPIKE-1031. ------------------------------------------ Resolution: Fixed Merged as: https://github.com/apache/deltaspike/commit/9ab5c5cac3a97c63e31858992f1046fa4fcd31cb Thanks for the PR. > Update profiles for Wildfly > --------------------------- > > Key: DELTASPIKE-1031 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1031 > Project: DeltaSpike > Issue Type: Improvement > Components: Configuration, Tests > Affects Versions: 1.5.1 > Reporter: Matej Novotny > Assignee: Rafael Benevides > Fix For: 1.5.2 > > > Taking a closer look at how test structure looks like, I saw that running > tests against Wildfly: > {{mvn clean verify -Pwildfly-managed}} > will launch Arquillian profile named {{jbossas-managed-7}}. > Similar situation is with remote profile (and maybe other tiny bits). > This naming seems inappropriate and highly confusing when (for instance) you > need to temper with Arq. settings in order to debug code. > I would suggest adding separate profiles to {{arquillian-jboss.xml}}. > Apart from this, what do you think about updating the default WFLY from 8 to > 9 (or even 10, there is CR4 already)? > Will send a PR with these tiny changes soon. -- This message was sent by Atlassian JIRA (v6.3.4#6332)