Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-984

Weld should not require application server specific changes to a war

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • None

    Description

      It should especially not require different content in the same file: that makes it almost impossible to solve.

      "Maven profiles" are NOT a solution: you should only build once during a release (and on hudson for every commit).
      The build output shouldn't differ based on the profile or build platform (strong maven guideline), because you can only deploy 1 variant to nexus under a certain GAV.
      Furthermore, it should be possible to do exploded war deployments straight from the IDE to different appservers (jboss 7, jetty, tomcat) without having to run maven.
      Similar for arquillian tests.

      See dependent issues for the specific things that cause problems.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users AS7-2119 Portable war: Weld deployment on JBoss AS 7 should not require to remove the WeldListener line from the web.xml

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Feature Request - Feature requests from customers and/or users WELD-985 Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WELD-1581 ServletContainerInitializer implementation for booting Weld

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: