[
https://issues.apache.org/jira/browse/MWAR-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Kurz updated MWAR-441:
----------------------------
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
and was wondering why this wasn't created as a File type parameter with a
default of: *${project.build.directory}/${project.build.finalName}/WEB-INF/lib*
since then you
WEB-INF/lib/
could be specified as either an absolute path or a path relative to *basedir*,
like
If this seems like a decent idea I can try to work on a patch,.
was:
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* (or maybe something in
META-INF).
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 saying this should be the default, but it would be nice to be able to
get stale stuff deleted from these other locations too.
I didn't see this come up and specifically get rejected on earlier issues like
*MWAR-433*, Also don't see a way how to do this today but please let me know
if I'm missing something.
I'd think this could be done and achieve backwards compatibility by treating
the
If this seems like a decent idea I can try to work on a patch, (though have
never contributed to one of the core Maven plugins).
> 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
> and was wondering why this wasn't created as a File type parameter with a
> default of:
> *${project.build.directory}/${project.build.finalName}/WEB-INF/lib*
> since then you
> WEB-INF/lib/
>
> could be specified as either an absolute path or a path relative to
> *basedir*, like
> If this seems like a decent idea I can try to work on a patch,.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
