[
https://jira.codehaus.org/browse/MRELEASE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-658.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> tagBase parameter for release plugin is partially ignored
> ---------------------------------------------------------
>
> Key: MRELEASE-658
> URL: https://jira.codehaus.org/browse/MRELEASE-658
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_21, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_21\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
> Reporter: David Bilge
>
> Using a different directory layout (tags/project instead of project/tags) I
> configured the tagBase as described on the maven site:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.1</version>
> <configuration>
> <tagBase>http://[pathToSvnRepo]/tags/projectName/</tagBase>
> </configuration>
> </plugin>
> Calling release:prepare, everything works correctly; even the scm info is
> changed exactly as expected. But, when the commit to create the tag is
> executed, it fails with an error like "path
> http://[pathToSvnRepo]/trunk/projectName/tags/1.7 does not exist" (wording
> might be different).
> Using maven 2 works flawlessly.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
