[
http://jira.codehaus.org/browse/SCM-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176522#action_176522
]
Baptiste MATHUS commented on SCM-468:
-------------------------------------
{quote}we can only update developerConnection as it could be different from
connection.
Maybe adding a parameter which says duplicate dev cnx to cnx.{quote}
Agreed. And yes, adding a parameter to just duplicate values would be great.
As discussed on the ML, I guess we could try to derive connection and url from
developerConnection. But let's start small and maybe do this later.
> Add scm:update-scm-tag
> ----------------------
>
> Key: SCM-468
> URL: http://jira.codehaus.org/browse/SCM-468
> Project: Maven SCM
> Issue Type: New Feature
> Components: maven-plugin
> Affects Versions: 1.2
> Reporter: Baptiste MATHUS
> Priority: Minor
>
> In each pom, maven users have to maintain the <scm /> xxxConnection tags to
> match the actual location of the project.
> When you checkout or move a project in the repository tree, those tags become
> incorrect. So you have to update them manually and take care for typos.
> As the information is present in the scm metadata (subversion, for me, by
> using "svn info"), those tags could be simply updated automatically by such a
> goal.
> Obviously, this goal would be even more useful when being ran at the root of
> a multimodule project.
> Thanks a lot.
> Cheers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
