Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for WildFly 10 and JBoss EAP 7 #73

Open
cardil opened this issue Mar 8, 2016 · 2 comments
Open

Add support for WildFly 10 and JBoss EAP 7 #73

cardil opened this issue Mar 8, 2016 · 2 comments

Comments

@cardil
Copy link
Collaborator

cardil commented Mar 8, 2016

About

We need to add support for WildFly 10 and JBoss EAP 7

WildFly 10.0.0.Final was released 2016-01-29 and EAP 7 will be released soon (7.0.0 Beta was released 2015-12-16).

Probable scope of change

@cardil
Copy link
Collaborator Author

cardil commented Jun 20, 2016

It looks like Wildfly 10 have moved init scripts to: docs/contrib/scripts:

|-- README.md
|-- init.d
|   |-- wildfly-init-debian.sh
|   |-- wildfly-init-redhat.sh
|   `-- wildfly.conf
|-- service
|   |-- amd64
|   |   `-- wildfly-service.exe
|   |-- service.bat
|   |-- wildfly-mgr.exe
|   `-- wildfly-service.exe
`-- systemd
    |-- README
    |-- launch.sh
    |-- wildfly.conf
    `-- wildfly.service

4 directories, 12 files

While JBoss EAP 7.0 still got them inside `bin/init.d/ directory, but only for RHEL:

.
|-- jboss-eap-rhel.sh
`-- jboss-eap.conf

0 directories, 2 files

I think the best solution for EAP for now is to embed scripts from WildFly into COI module. @coi-gov-pl/jboss-puppet-team please react to this post - Yah or Nah?

@therek
Copy link
Collaborator

therek commented Jun 21, 2016

👍

cardil pushed a commit that referenced this issue Jun 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@therek @cardil and others