[
http://jira.codehaus.org/browse/MSHARED-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MSHARED-63.
-------------------------------
Assignee: Olivier Lamy
Resolution: Duplicate
Duplicate with MSHARED-60.
You can test with the current war plugin trunk.
If you have any trouble please reopen the issue.
> Filtering Resources does not match patterns strictly
> ----------------------------------------------------
>
> Key: MSHARED-63
> URL: http://jira.codehaus.org/browse/MSHARED-63
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
> Affects Versions: maven-filtering-1.0-beta-1
> Reporter: Walter White
> Assignee: Olivier Lamy
>
> When using Maven Filtering, maven-war-plugin, variables within the JSP that
> do not correspond to configured properties are updated as well ie.
> [code]
> ${users.id}
> ${user.id}
> ${adfadfadf.id}
> [/code]
> All of those patterns are matched to the project id which causes the JSP
> throw an exception. Having these properties set at build time lets me
> configure the context.path and links dynamically depending on the
> environment. The problem appears to be associated with the plexus pattern
> matching plugin as it is what decides to match any variable ending in .id
> I suggest that an option is added to configure which patterns are matched and
> if the pattern matching is strict. For example, in my JSPs, it would be
> ideal to only allow @context.path@ and not ${users.id} so the variables
> within the JSP remain just that and configured properties are updated
> accordingly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
