Details

    • Type: New Feature New Feature
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None

      Description

      It would be cool if Gradle supported some notion of war overlays/compositing (http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html) out of the box (integrated with dependency management). We rely on this feature rather extensively to perform customizations of third party war files.

        Activity

        Hide
        Davide Cavestro added a comment - - edited

        Really needed for customizing web applications (even home made) and getting a good IDE integration even for war projects (take a look at STS-1314 discussion).
        Maybe this could also benefit from GRADLE-1014?

        Show
        Davide Cavestro added a comment - - edited Really needed for customizing web applications (even home made) and getting a good IDE integration even for war projects (take a look at STS-1314 discussion ). Maybe this could also benefit from GRADLE-1014 ?
        Hide
        Davide Cavestro added a comment - - edited

        I hope this issue should not remain a minor priority RFE.
        I think here the focus doesn't lie as much in having any way to produce a war (we can still obtain it in several ways thanks to gradle flexibility) but rather in composing war artifacts based on dependencies between wars, with proper management for provided deps transitivity.
        In other words a war project by convention could get transient deps and web contents from other war projects/artifacts it depends upon.
        It would be great also having a way to obtain war overlay for gradle projects that enforces complete IDE integration i.e. a declarative approach that lets the tooling api expose enough info about merged resources in order to support the ide on reflecting the overlay as needed (we use eclipse/STS).
        I've opened a dedicated thread on the user mailing list.

        Show
        Davide Cavestro added a comment - - edited I hope this issue should not remain a minor priority RFE. I think here the focus doesn't lie as much in having any way to produce a war (we can still obtain it in several ways thanks to gradle flexibility) but rather in composing war artifacts based on dependencies between wars, with proper management for provided deps transitivity. In other words a war project by convention could get transient deps and web contents from other war projects/artifacts it depends upon. It would be great also having a way to obtain war overlay for gradle projects that enforces complete IDE integration i.e. a declarative approach that lets the tooling api expose enough info about merged resources in order to support the ide on reflecting the overlay as needed (we use eclipse/STS). I've opened a dedicated thread on the user mailing list.

          People

          • Assignee:
            Unassigned
            Reporter:
            Aaron Hamid
          • Votes:
            22 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

            • Created:
              Updated:

              Development