Is this not caused by the tagbase defined in the main pom?
<plugin>
349 <artifactId>maven-release-plugin</artifactId>
350 <configuration>
351
<tagBase>https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/</tagBase>
352 </configuration>
353 </plugin>
On 03/23/2011 09:48 AM, Igor Drobiazko wrote:
Looks like this commit cause by the plugin is the reason. Does anyone has a
clue what's happening?
http://svn.apache.org/viewvc?view=revision&revision=1084504
On Wed, Mar 23, 2011 at 9:46 AM, Igor Drobiazko<[email protected]>wrote:
How is it possible that maven release plugin creates such a strange tag?
https://svn.apache.org/repos/asf/tapestry/tapestry5/tags/releases/5.2.5/pom.xml
The version and scm is just wrong.
On Tue, Mar 22, 2011 at 8:49 AM, Igor Drobiazko<[email protected]>wrote:
Fortunately I'm on Mac. I'll try adding
<mavenExecutorId>forked-path</mavenExecutorId> to the release plugin.
On Tue, Mar 22, 2011 at 8:13 AM, Massimo Lusetti<[email protected]>wrote:
On Tue, Mar 22, 2011 at 7:34 AM, Kalle Korhonen
<[email protected]> wrote:
Interactively? i.e. you don't have encrypted key in your settings.xml?
You have to specify<mavenExecutorId>forked-path</mavenExecutorId>
see http://jira.codehaus.org/browse/MGPG-9
and http://svn.apache.org/repos/asf/shiro/trunk/pom.xml
Yeah It's a nightmare and I cannot even imagine on Windows...
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Best regards,
Igor Drobiazko
http://tapestry5.de
--
Best regards,
Igor Drobiazko
http://tapestry5.de
