You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2019/11/10 20:56:00 UTC

[jira] [Closed] (MWAR-375) Remove the useCache with it's implementation

     [ https://issues.apache.org/jira/browse/MWAR-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MWAR-375.
-------------------------------
    Fix Version/s:     (was: next-release)
                       (was: more-investigation)
                   3.2.4
         Assignee: Robert Scholte
       Resolution: Fixed

Fixed in [88731b2a108e8cb72ea042061ec90641e7a0f0bc|https://gitbox.apache.org/repos/asf?p=maven-war-plugin.git;a=commit;h=88731b2a108e8cb72ea042061ec90641e7a0f0bc]

> Remove the useCache with it's implementation
> --------------------------------------------
>
>                 Key: MWAR-375
>                 URL: https://issues.apache.org/jira/browse/MWAR-375
>             Project: Maven WAR Plugin
>          Issue Type: Improvement
>            Reporter: Karl Heinz Marbaise
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 3.2.4
>
>
> The useCache can activate some caching within the maven-war-plugin, but the question is why is it needed? As described in the description of the parameter for multiple runs? Why should maven-war-plugin run multiple times within the same module?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)