You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by hanasaki <ha...@hanaden.com> on 2010/03/09 05:09:18 UTC
why does mvn release replace ${groupId} in with actual values?
Did a maven release and had "connection" information in the <scm>
section. After the release, the new pom with updated coordinates in its
<version> section had replaced the ${groupId}/${artifactId}/trunk in the
new pom with the Actual values.
How can the dynamic nature be retained?
Where is the algorithm for how the connection URL's are updated?
TIA
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: why does mvn release replace ${groupId} in with actual values?
Posted by Martin Höller <ma...@xss.co.at>.
Am Dienstag, 9. März 2010 05:09:18 schrieb hanasaki:
> Did a maven release and had "connection" information in the <scm>
> section. After the release, the new pom with updated coordinates in its
> <version> section had replaced the ${groupId}/${artifactId}/trunk in the
> new pom with the Actual values.
http://jira.codehaus.org/browse/MRELEASE-128
hth,
- martin