Re: release:prepare issue with Mercurial SCM

[Andrew Hughes <ah...@gmail.com>]

Hi Andrew,

Do you mind if I ask you a question? How do you provide the scm+hg maven
plugin with your push credentials (username+password)? I'm assuming this is
something in the settings.xml?

I am trying to get this sourceforge project released....
http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/54921eaf7464/pom.xml

<http://gwt-openlayers.hg.sourceforge.net/hgweb/gwt-openlayers/gwt-openlayers/file/54921eaf7464/pom.xml>Thanks
in advance,
Andrew


On Tue, Jul 27, 2010 at 2:24 AM, Andrew Westberg <andrew@simplifiedlogic.com
> wrote:

> I'm trying to deploy my first release build of a project to my nexus
> server.
>  My scm configuration looks like this:
>
>  <scm>
>
>
> <connection>scm:hg:ssh://fortis//data/mercurial/projects/JarEncryptor</connection>
>
>
> <developerConnection>scm:hg:ssh://fortis//data/mercurial/projects/JarEncryptor</developerConnection>
>  </scm>
>
> I need the extra / after fortis since the repository is on the /data
> partition of the remote filesystem.
>
> The problem is that when I use the maven release:prepare plugin, it ALWAYS
> strips out the extra slash when doing the push command and then I get the
> following error message:
>
> [INFO] Checking in modified POMs...
> [INFO] EXECUTING: cmd.exe /X /C "hg commit --message
> "[maven-release-plugin]
> prepare release jar-enc
> ryptor-aggregator-1.0" C:\Development\workspace\MyProject\pom.xml
> C:\Development\workspace\MyPro
> ject\nitrolm-encryptx\pom.xml
> C:\Development\workspace\JarEncryptor\nitrolm-encryptx-maven-plugin\
> pom.xml C:\Development\workspace\JarEncryptor\nitrolm-encryptx-ant\pom.xml"
> [INFO] EXECUTING: cmd.exe /X /C "hg push
> ssh://fortis/data/mercurial/projects/JarEncryptor"
> [ERROR]
> EXECUTION FAILED
>  Execution of cmd : push failed with exit code: -1.
>  Working directory was:
>    C:\Development\workspace\JarEncryptor
>  Your Hg installation seems to be valid and complete.
>    Hg version: 1.5.2 (OK)
>
>
> Any ideas on how to get around this?  I already tried putting four slashes
> in my <scm> configuration, but it stripped out all but one.
>
> --
> Andrew Westberg
>