You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by manovotn <gi...@git.apache.org> on 2015/11/20 13:22:35 UTC

[GitHub] deltaspike pull request: DELTASPIKE-1031 update profiles for WFLY

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 <ma...@redhat.com>
Date:   2015-11-20T12:13:20Z

    DELTASPIKE-1031 update profiles for WFLY

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] deltaspike pull request #46: DELTASPIKE-1031 update profiles for WFLY

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---