[jboss-jira] [JBoss JIRA] (WFLY-4081) Do not force that the exploded directory ends with ".war"

[Brian Stansberry (JIRA)]

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

Brian Stansberry edited comment on WFLY-4081 at 12/23/14 7:15 PM:
------------------------------------------------------------------

Low-level CLI syntax for the above high-level command:

{code}
[standalone at localhost:9990 /] /deployment=hello:add(runtime-name=helloworld.war,enabled=true,content=[{path=/home/me/tmp/hello,archive=false}])
{"outcome" => "success"}
{code}

The CLI echo-dmr command translates that into DMR text format, so a custom client like a plugin that uses a ModelControllerClient would construct an operation ModelNode like this output from the echo-dmr command:

{code}
[standalone at localhost:9990 /] echo-dmr /deployment=hello:add(runtime-name=helloworld.war,enabled=true,content=[{path=/home/me/tmp/hello,archive=false}])
{
    "address" => [("deployment" => "hello")],
    "operation" => "add",
    "content" => [{
        "path" => "/home/me/tmp/hello",
        "archive" => "false"
    }],
    "runtime-name" => "helloworld.war",
    "enabled" => true
}
{code} 


was (Author: brian.stansberry):
Low-level CLI syntax for the above high-level command:

{code}
[standalone at localhost:9990 /] /deployment=hello:add(runtime-name=helloworld.war,enabled=true,content=[{path=/home/me/tmp/hello,archive=false}])
{"outcome" => "success"}
{code}

The CLI echo-dmr command translates that into DMR text format, so a custom client like a plugin that uses a ModelControllerClient would construct an operation ModelNode like this output from the echo-dmr command:

{code}
[standalone at localhost:9990 /] echo-dmr /deployment=hello:add(runtime-name=helloworld.war,enabled=true,content=[{path=/Users/bstansberry/tmp/hello,archive=false}])
{
    "address" => [("deployment" => "hello")],
    "operation" => "add",
    "content" => [{
        "path" => "/home/mey/tmp/hello",
        "archive" => "false"
    }],
    "runtime-name" => "helloworld.war",
    "enabled" => true
}
{code} 

> Do not force that the exploded directory ends with ".war"
> ---------------------------------------------------------
>
>                 Key: WFLY-4081
>                 URL: https://issues.jboss.org/browse/WFLY-4081
>             Project: WildFly
>          Issue Type: Enhancement
>            Reporter: Geoffrey De Smet
>            Assignee: Jason Greene
>
> In a standard webapp, maven creates the following directory and file:
> // Exploded directory
> target/mywebapp-1.0/
> // War file
> target/mywebapp-1.0.war
> *Unfortunately, WildFly forces that exploded directories should have the suffix ".war"*. At least the IntelliJ JBoss app server plugin enforces this, if that's no longer the case, they should fix it asap. This has 2 side effects:
> 1) Every noob fails to deploy an exploded dir to WildFly in IntelliJ. By the time they realize that it's because they haven't adjusted the exploded artifact's output path, they're already using Jetty or Tomcat (which "just work" in IntelliJ).
> 2) As a result, maven and IntelliJ are potentially incompatible for WildFly:
> If you just suffix the exploded directory with ".war", the exploded directory clashes with maven's war file.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)