[
https://issues.jboss.org/browse/WFLY-4081?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-4081:
----------------------------------------
IMO this is primarily a problem with Intellij.
This works fine from the CLI (with ~/tmp/hello being an exploded deployment):
{code}
[standalone@localhost:9990 /] deploy ~/tmp/hello --runtime-name=helloworld.war
--unmanaged
{code}
That's CLI command syntax that results in a low level management op that Intellij
could certainly execute as well. The key part is adding the "runtime-name"
parameter to the op, with a value that indicates the deployment is a war. Presumably the
tooling knows this.
Perhaps there is still a valid feature request here, if the idea is somehow WildFly just
knows it's a war. But I doubt that will change. Note that Tomcat can make an
assumption about a deployment just being a war because it doesn't deploy ears and ejb
jars and sars and datasources and driver jars and...
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.8#6338)