[MWAR-441] Allow "outdatedCheckPath" parameter to be set to cover web app dir root (everything in the web app directory)

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.3.1
• Fix Version/s: 3.3.2
• Assignee: Unassigned
• Reporter: Scott Kurz
• Created: 15/Apr/21 01:44
• Updated: 09/May/21 15:32
• Resolved: 09/May/21 14:59

Description

I would like to subject something copied to the WAR root, e.g. a JSP to the same "outdated" check for goals like war:exploded . 

I don't see a way to do that currently.   An empty String or absent config value triggers the default of WEB-INF/lib/

I'm not too familiar with mojo File-typed parameters.   Is there a construct or pattern that lets you use either a relative or absolute path like you can with the webappDirectory, warSourceDirectory parameters, but relative to the webappDirectory rather than basedir?

E.g. for warSourceDirectory I can specify:  src/main/webapp  or an absolute path.  If I could do something like that for outdatedCheckPath today that would meet my needs.    But maybe this parameter resolution only works conveniently relative to the basedir? 

 

If this parameter must remain a "prefix" or path relative to the webappDirectory, maybe it just needs a special syntax like  '.'  or '*' to cover everything.

 

Issue Links

• relates to: MWAR-433 Maven WAR plugin is deleting files generated by other plugins after upgrading to 3.3.0
• links to: GitHub Pull Request #19