[jira] [Commented] (DELTASPIKE-1031) Update profiles for Wildfly

2015-11-20 Thread Matej Novotny (JIRA)

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15016712#comment-15016712
 ] 

Matej Novotny commented on DELTASPIKE-1031:
---

PR can be found at -> https://github.com/apache/deltaspike/pull/46

> 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
>
> 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)


[jira] [Commented] (DELTASPIKE-1031) Update profiles for Wildfly

2015-11-20 Thread Gerhard Petracek (JIRA)

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15017738#comment-15017738
 ] 

Gerhard Petracek commented on DELTASPIKE-1031:
--

[~manovotn] thx for improving the build conifg.
fyi the most important test-profiles are the build-managed profiles, because we 
use them for https://builds.apache.org/view/A-D/view/DeltaSpike/

> 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)


[jira] [Commented] (DELTASPIKE-1031) Update profiles for Wildfly

2015-11-20 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/DELTASPIKE-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15016709#comment-15016709
 ] 

ASF GitHub Bot commented on DELTASPIKE-1031:


GitHub user manovotn opened a pull request:

https://github.com/apache/deltaspike/pull/46

DELTASPIKE-1031 update profiles for WFLY

Created separate arq. profiles for managed and remote WFLY. This should 
make it obvious which profiles are related to which server in case one needs to 
modify the settings.

I also updated WFLY default version to latest Final release which is 9.0.2. 
Although I think there could even be WFLY 10 (currently at CR4). But should you 
insist on leaving it at 8, I will revert it.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/manovotn/deltaspike master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/deltaspike/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit cbcc9cb7159d7070c7c563986c1b641dcdfe9a2a
Author: Matej Novotny 
Date:   2015-11-20T12:13:20Z

DELTASPIKE-1031 update profiles for WFLY




> 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
>
> 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)