[
http://jira.codehaus.org/browse/MRELEASE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MRELEASE-434.
---------------------------------
Assignee: Olivier Lamy
Resolution: Not A Bug
Yes sure we trust what the user put on the pom scm element.
If you prefer to old behaviour you can use remotetagging=false
> Assumes scm.url is Current Directory for Remote Tagging
> -------------------------------------------------------
>
> Key: MRELEASE-434
> URL: http://jira.codehaus.org/browse/MRELEASE-434
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-9
> Reporter: Ben Tatham
> Assignee: Olivier Lamy
>
> With the addition of remoteTagging=true, based on the testing I have done,
> the release plugin is doing a remote tag of the url defined in the scm.url
> property, which I think comes from developerConnection.
> If this is incorrect, and that url doesn't exist, than it fails.
> If this is incorrect, and the url does exist, then the user will get
> unexpected results, not to mention that you just ran the tests against
> something different than what will be released (although they will be run
> again at release:perform)
> Is this the intended behaviour? Or is my testing taking me to the wrong
> conclusions?
--
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
