Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4081

Do not force that the exploded directory ends with ".war"

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  brian.stansberry Brian Stansberry
                  Reporter:
                  ge0ffrey Geoffrey De Smet
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: