You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by huser <mp...@atxg.com> on 2009/04/06 17:32:59 UTC
maven release plugin issue
Hi,
I setup the maven release plugin as
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9-SNAPSHOT</version>
<configuration>
<remoteTagging>true</remoteTagging>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Prelease</arguments>
</configuration>
When I run mvn release:plugin it is not able to tag SVN.
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: '/abc_repos/sip/tags' path not found
This is because I am running the plugin inside a module, which exists under
a SVN repo. The path listed above does not exist. The correct path should be
be /abc_repos/tags. How can I run this ?
thanks,
--
View this message in context: http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven release plugin issue
Posted by huser <mp...@atxg.com>.
I am using tagBase and still the same result
[INFO] Tagging release with the label REL1.0-TEST...
[INFO] Executing: svn --non-interactive copy --file
C:\DOCUME~1\huser\LOCALS~
1\Temp\maven-scm-1923501528.commit .
https://domain1.na.abcglobal.com/abc_repos
/sip/tags/REL1.0-TEST
[INFO] Working directory: C:\ws17\sip
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: '/abc_repos/sip/tags' path not found
The tagging needs to be done under /abc_repos/projectA/tags. "sip" is a
module under projectA, which is where I am running the maven release plugin
from.
POM.xml
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<configuration>
<tagBase>https://domain1.na.abcglobal.com/abc_repos/projectA/tags</tagBase>
<remoteTagging>false</remoteTagging>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Prelease</arguments>
</configuration>
</plugin>
Olivier Lamy wrote:
>
> Have a look at :
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#tagBase
>
> HTH,
> --
> Olivier
>
> 2009/4/6 huser <mp...@atxg.com>:
>>
>> Here is what i did:
>>
>> - Changed the version to 2.0-beta-9
>> - Set remoteTagging to false
>> - scm element is listed as
>>
>> The release plugin commits the POM's even if tagging fails. And tagging
>> does
>> fail, because of incorrect location. Why is SVN trying to tag
>> /abc_repos/sip/tags instead of /abc_repos/tags ?
>>
>> [INFO] Executing: svn --non-interactive copy --file
>> C:\DOCUME~1\huser\LOCALS~
>> 1\Temp\maven-scm-1466134858.commit .
>> https://domain1.na.abcglobal.com/abc_repos
>> /sip/tags/REL_1.0-TEST
>> [INFO] Working directory: C:\ws17\sip
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to tag SCM
>> Provider message:
>> The svn tag command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: '/abc_repos/sip/tags' path not found
>>
>> POM now looks like:
>>
>>
>> <scm>
>>
>> <connection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</connection>
>>
>> <developerConnection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</developerConnection>
>> <url>https://domain1.na.abcglobal.com/abc_repos</url>
>>
>> </scm>
>>
>> <plugin>
>>
>> <groupId>org.apache.maven.plugins</group
>> Id>
>>
>> <artifactId>maven-release-plugin</artifactId>
>> <version>2.0-beta-9</version>
>> <configuration>
>>
>> <remoteTagging>false</remoteTagg
>> ing>
>>
>> <useReleaseProfile>false</useReleaseProfile>
>> <goals>deploy</goals>
>>
>> <arguments>-Prelease</arguments>
>> </configuration>
>> </plugin>
>>
>>
>>
>> Olivier Lamy wrote:
>>>
>>> Hi,
>>> First use a released version of the plugin : 2.0-beta-9.
>>> Then two options :
>>> - remoteTagging to false
>>> - add a scm element in your pom.
>>>
>>> --
>>> Olivier
>>>
>>> 2009/4/6 huser <mp...@atxg.com>:
>>>>
>>>> Hi,
>>>>
>>>> I setup the maven release plugin as
>>>> <plugin>
>>>>
>>>> <groupId>org.apache.maven.plugins</groupId>
>>>>
>>>> <artifactId>maven-release-plugin</artifactId>
>>>>
>>>> <version>2.0-beta-9-SNAPSHOT</version>
>>>> <configuration>
>>>>
>>>> <remoteTagging>true</remoteTagging>
>>>>
>>>> <useReleaseProfile>false</useReleaseProfile>
>>>> <goals>deploy</goals>
>>>>
>>>> <arguments>-Prelease</arguments>
>>>> </configuration>
>>>>
>>>> When I run mvn release:plugin it is not able to tag SVN.
>>>>
>>>> Provider message:
>>>> The svn tag command failed.
>>>> Command output:
>>>> svn: Commit failed (details follow):
>>>> svn: '/abc_repos/sip/tags' path not found
>>>>
>>>> This is because I am running the plugin inside a module, which exists
>>>> under
>>>> a SVN repo. The path listed above does not exist. The correct path
>>>> should
>>>> be
>>>> be /abc_repos/tags. How can I run this ?
>>>>
>>>> thanks,
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
>>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22914943.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/maven-release-plugin-issue-tp22911245p22918513.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven release plugin issue
Posted by Olivier Lamy <ol...@apache.org>.
Have a look at :
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#tagBase
HTH,
--
Olivier
2009/4/6 huser <mp...@atxg.com>:
>
> Here is what i did:
>
> - Changed the version to 2.0-beta-9
> - Set remoteTagging to false
> - scm element is listed as
>
> The release plugin commits the POM's even if tagging fails. And tagging does
> fail, because of incorrect location. Why is SVN trying to tag
> /abc_repos/sip/tags instead of /abc_repos/tags ?
>
> [INFO] Executing: svn --non-interactive copy --file
> C:\DOCUME~1\huser\LOCALS~
> 1\Temp\maven-scm-1466134858.commit .
> https://domain1.na.abcglobal.com/abc_repos
> /sip/tags/REL_1.0-TEST
> [INFO] Working directory: C:\ws17\sip
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: '/abc_repos/sip/tags' path not found
>
> POM now looks like:
>
>
> <scm>
>
> <connection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</connection>
>
> <developerConnection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</developerConnection>
> <url>https://domain1.na.abcglobal.com/abc_repos</url>
>
> </scm>
>
> <plugin>
>
> <groupId>org.apache.maven.plugins</group
> Id>
>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-9</version>
> <configuration>
>
> <remoteTagging>false</remoteTagg
> ing>
>
> <useReleaseProfile>false</useReleaseProfile>
> <goals>deploy</goals>
>
> <arguments>-Prelease</arguments>
> </configuration>
> </plugin>
>
>
>
> Olivier Lamy wrote:
>>
>> Hi,
>> First use a released version of the plugin : 2.0-beta-9.
>> Then two options :
>> - remoteTagging to false
>> - add a scm element in your pom.
>>
>> --
>> Olivier
>>
>> 2009/4/6 huser <mp...@atxg.com>:
>>>
>>> Hi,
>>>
>>> I setup the maven release plugin as
>>> <plugin>
>>>
>>> <groupId>org.apache.maven.plugins</groupId>
>>>
>>> <artifactId>maven-release-plugin</artifactId>
>>>
>>> <version>2.0-beta-9-SNAPSHOT</version>
>>> <configuration>
>>>
>>> <remoteTagging>true</remoteTagging>
>>>
>>> <useReleaseProfile>false</useReleaseProfile>
>>> <goals>deploy</goals>
>>>
>>> <arguments>-Prelease</arguments>
>>> </configuration>
>>>
>>> When I run mvn release:plugin it is not able to tag SVN.
>>>
>>> Provider message:
>>> The svn tag command failed.
>>> Command output:
>>> svn: Commit failed (details follow):
>>> svn: '/abc_repos/sip/tags' path not found
>>>
>>> This is because I am running the plugin inside a module, which exists
>>> under
>>> a SVN repo. The path listed above does not exist. The correct path should
>>> be
>>> be /abc_repos/tags. How can I run this ?
>>>
>>> thanks,
>>> --
>>> View this message in context:
>>> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/maven-release-plugin-issue-tp22911245p22914943.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven release plugin issue
Posted by huser <mp...@atxg.com>.
Here is what i did:
- Changed the version to 2.0-beta-9
- Set remoteTagging to false
- scm element is listed as
The release plugin commits the POM's even if tagging fails. And tagging does
fail, because of incorrect location. Why is SVN trying to tag
/abc_repos/sip/tags instead of /abc_repos/tags ?
[INFO] Executing: svn --non-interactive copy --file
C:\DOCUME~1\huser\LOCALS~
1\Temp\maven-scm-1466134858.commit .
https://domain1.na.abcglobal.com/abc_repos
/sip/tags/REL_1.0-TEST
[INFO] Working directory: C:\ws17\sip
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: '/abc_repos/sip/tags' path not found
POM now looks like:
<scm>
<connection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</connection>
<developerConnection>scm:svn:https://domain1.na.abcglobal.com/abc_repos</developerConnection>
<url>https://domain1.na.abcglobal.com/abc_repos</url>
</scm>
<plugin>
<groupId>org.apache.maven.plugins</group
Id>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<configuration>
<remoteTagging>false</remoteTagg
ing>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Prelease</arguments>
</configuration>
</plugin>
Olivier Lamy wrote:
>
> Hi,
> First use a released version of the plugin : 2.0-beta-9.
> Then two options :
> - remoteTagging to false
> - add a scm element in your pom.
>
> --
> Olivier
>
> 2009/4/6 huser <mp...@atxg.com>:
>>
>> Hi,
>>
>> I setup the maven release plugin as
>> <plugin>
>>
>> <groupId>org.apache.maven.plugins</groupId>
>>
>> <artifactId>maven-release-plugin</artifactId>
>>
>> <version>2.0-beta-9-SNAPSHOT</version>
>> <configuration>
>>
>> <remoteTagging>true</remoteTagging>
>>
>> <useReleaseProfile>false</useReleaseProfile>
>> <goals>deploy</goals>
>>
>> <arguments>-Prelease</arguments>
>> </configuration>
>>
>> When I run mvn release:plugin it is not able to tag SVN.
>>
>> Provider message:
>> The svn tag command failed.
>> Command output:
>> svn: Commit failed (details follow):
>> svn: '/abc_repos/sip/tags' path not found
>>
>> This is because I am running the plugin inside a module, which exists
>> under
>> a SVN repo. The path listed above does not exist. The correct path should
>> be
>> be /abc_repos/tags. How can I run this ?
>>
>> thanks,
>> --
>> View this message in context:
>> http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/maven-release-plugin-issue-tp22911245p22914943.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven release plugin issue
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
First use a released version of the plugin : 2.0-beta-9.
Then two options :
- remoteTagging to false
- add a scm element in your pom.
--
Olivier
2009/4/6 huser <mp...@atxg.com>:
>
> Hi,
>
> I setup the maven release plugin as
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-9-SNAPSHOT</version>
> <configuration>
> <remoteTagging>true</remoteTagging>
> <useReleaseProfile>false</useReleaseProfile>
> <goals>deploy</goals>
> <arguments>-Prelease</arguments>
> </configuration>
>
> When I run mvn release:plugin it is not able to tag SVN.
>
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: '/abc_repos/sip/tags' path not found
>
> This is because I am running the plugin inside a module, which exists under
> a SVN repo. The path listed above does not exist. The correct path should be
> be /abc_repos/tags. How can I run this ?
>
> thanks,
> --
> View this message in context: http://www.nabble.com/maven-release-plugin-issue-tp22911245p22911245.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org