I realize this plugin hasn't been updated in a while, but I thought I what
throw this question out there to see if anyone has any helpful thoughts.
I am using the plugin to read in a set of properties using the
ReadPropertiesMojo. The mojo is bound to the generate-resources phase. The
properties are used in the pom in a <properties/> block, to essentially
rename the properties. For example, in the properties file, I will have a
property foo.jetty.port and in the properties block in the pom I have:
<jetty.port>${foo.jetty.port}</jetty.port>
This seems to mostly work correctly. If I turn on debug logging, I can see
that the jetty.port property gets set to the value of foo.jetty.port in the
properties file. Resource filtering seems to correctly resolve the value of
jetty.port. The problem is that for configuration in some plugins
(maven-jetty-plugin, exec plugin), if they use the value of the jetty.port
property, it resolves to null, as if the configuration read in the value of
jetty.port AND resolved it before the read properties mojo was run (which
would be ${foo.jetty.port}). Is this analysis correct? Is there any way to
make this work? It seems like the problem is that whatever is handling
plugin configuration needs to resolve property values at a later time, but
that seems like a core change.
Any insights would be appreciated.
Kelly
