[ https://issues.apache.org/jira/browse/JCR-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1788. -------------------------------- Resolution: Invalid Assignee: Jukka Zitting Resolving as Invalid. This is an issue with the Maven resources plugin. See http://jira.codehaus.org/browse/MRESOURCES-29 for the related feature request (escape mechanism). This feature is implemented in the upcoming 2.3 release of the resources plugin. > Maven variable collision > ------------------------ > > Key: JCR-1788 > URL: https://issues.apache.org/jira/browse/JCR-1788 > Project: Jackrabbit > Issue Type: Bug > Components: config > Environment: maven 2.0.9, 2.1.0-M1 > Reporter: Stephane Landelle > Assignee: Jukka Zitting > Attachments: maven-filtering-test.zip > > Original Estimate: 0.08h > Remaining Estimate: 0.08h > > The jackrabbit config file uses a variable ${wsp.name}. > This variable name is already used by maven during filtering and holds the > project name. > As a consequence, when trying to filter the file in order for example to > change the Cluster Node Id, the file gets corrupted. > Please find test project enclosed. > Patch is very simple : you can keep old variables for compatibility, just > duplicate variable with a jackrabbit specific name such as "jr.wsp.name" and > add in org.apache.jackrabbit.core.config.RepositoryConfigurationParser: > line 62: > /** Name of the repository name parser variable. */ > public static final String MAVEN_SUPPORTING_WORKSPACE_NAME_VARIABLE = > "jr.wsp.name"; > line 420: > // add a dupplicate that supports maven filtering > tmpVariables.put(MAVEN_SUPPORTING_WORKSPACE_NAME_VARIABLE, name); > This should even be done for other variables to avoid possible later > collisions. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.