[jboss-jira] [JBoss JIRA] (WFLY-3660) allow easy creation of executable war

[jieryn jieryn (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987495#comment-12987495 ] 

jieryn jieryn commented on WFLY-3660:
-------------------------------------

The other tools I mentioned, they both end up expanding themselves into a particular directory (e.g. $CWD/.distribution in TomEE's case). They basically just unpack a fully working distribution, and then invoke the startup. I believe the main class does the unpacking, and then at the end there is a fork to launch. I find that acceptable, it seems to be the norm (even tools like JenkinsCI do that with their java -jar jenkins.war, which creates a $HOME/.jenkins unpack and execution).

> allow easy creation of executable war
> -------------------------------------
>
>                 Key: WFLY-3660
>                 URL: https://issues.jboss.org/browse/WFLY-3660
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Server
>    Affects Versions: 8.1.0.Final
>            Reporter: jieryn jieryn
>            Assignee: Jason Greene
>            Priority: Minor
>
> Other popular Servlet Containers and Application Servers support the building of an executable war bundle, via Apache Maven. This will allow you to easily bundle your WAR/EAR into an executable war which will unpack and launch the WAR/EAR, via java -jar myapp.war.
> http://tomcat.apache.org/maven-plugin-2.0/tomcat7-maven-plugin/exec-war-mojo.html
> http://rmannibucau.wordpress.com/2014/03/11/executable-jar-with-tomee-and-tomcat-maven-plugin/



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)