[
https://issues.apache.org/jira/browse/MWAR-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341467#comment-17341467
]
Hudson commented on MWAR-441:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-war-plugin » master #27
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-war-plugin/job/master/27/
> Allow "outdatedCheckPath" parameter to be set to cover web app dir root
> (everything in the web app directory)
> -------------------------------------------------------------------------------------------------------------
>
> Key: MWAR-441
> URL: https://issues.apache.org/jira/browse/MWAR-441
> Project: Maven WAR Plugin
> Issue Type: Improvement
> Affects Versions: 3.3.1
> Reporter: Scott Kurz
> Priority: Minor
>
> 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
