Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: maven-filtering-1.0-beta-1
-
Fix Version/s: None
-
Component/s: maven-filtering
-
Labels:None
-
Number of attachments :
Description
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.
Issue Links
| This issue duplicates: | ||||
| MSHARED-60 | Filtering ${foo.file} evaluates to in full path to pom.xml |
|
|
|
Certainly duplicate with
MSHARED-60.Can you try the current war plugin trunk it should be fixed ?
MSHARED-60. Can you try the current war plugin trunk it should be fixed ?