> POM causes it to be picked up by the plugin just fine. It's when the
> property is loaded by the other plugin that there's a problem. For some
> reason, maven doesn't seem to treat this the same as a property declared in
> the POM.
properties-m-p is a bit of a hack. The Maven team is pretty clear
about where properties should go -- in pom.xml, profiles.xml, or
settings.xml files ONLY.
> <port>1${tomcat.httpPort}</port>
Is there a good reason for not simply putting the port directly in the
pom? Or even in a profile?
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
