]
Brian Stansberry resolved WFLY-4081.
------------------------------------
Assignee: Brian Stansberry (was: Jason Greene)
Resolution: Won't Fix
I'm resolving this as "Won't Fix" as we already provide behavior to
satisfy the use case, and it appears this is primarily an issue with Intellij. They
commented on the Intellij bug tracker that they intend to fix the problem.
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: Brian Stansberry
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.