[
https://jira.codehaus.org/browse/MRESOURCES-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301768#comment-301768
]
Tim Pizey commented on MRESOURCES-169:
--------------------------------------
The problem seems to be in the tomcat plugin - the variables are in the
context, but the tomcat plugin is only reading the initial context, not the
final one.
> Silently fails to import properties from a properties file
> ----------------------------------------------------------
>
> Key: MRESOURCES-169
> URL: https://jira.codehaus.org/browse/MRESOURCES-169
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Components: filtering
> Environment: ubuntu/openjdk6/maven 3.0.4
> Reporter: Tim Pizey
>
> I have tried inherited from parent, defined in pom and with and without
> encoding:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-resources-plugin</artifactId>
> <version>2.5</version>
> <configuration>
> <encoding>${project.build.sourceEncoding}</encoding>
> </configuration>
> </plugin>
> invoked with
> <filters>
> <filter>/etc/${project.artifactId}/repository.properties</filter>
> </filters>
> This fails if the file does not exist, but if it does exist the properties
> are not included.
> I have tried the properties file as a normal key=value file and as an XML
> properties file.
> This mechanism would be REALLY useful if it worked, as it would enable
> passwords not to be stored in our SCM, nor in settings.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
