Please retry the same command line with -Dpassword="..." outside of
-Darguments="...". Moreover, -Dpassphrase is not a valid argument for the
goals you used.


2013/7/23 Adrien Ruffié <adriennolar...@hotmail.fr>

> No sorry I have try following command :
>
> mvn -Darguments="-Dmaven.test.skip=true -Pdistribution-packaging
> -Dpassword=mypassword" release:prepare release:perform --batch-mode
> -Dtag=Spring2013/005 -Dcom.myapp.frontline:myapp-webapp=Spring2013/005
> -Dcom.myapp.frontline:myapp-install-wizard=Spring2013/005
> -DreleaseVersion=Spring2013-005
> -DdevelopmentVersion=Spring2013-006-SNAPSHOT -Dpassword=mypassword
>
> I also try with passphrase like:
>
> mvn -Darguments="-Dmaven.test.skip=true -Pdistribution-packaging
> -Dpassphrase=mypassword" release:prepare release:perform --batch-mode
> -Dtag=Spring2013/005 -Dcom.myapp.frontline:myapp-webapp=Spring2013/005
> -Dcom.myapp.frontline:myapp-install-wizard=Spring2013/005
> -DreleaseVersion=Spring2013-005
> -DdevelopmentVersion=Spring2013-006-SNAPSHOT -Dpassphrase=mypassword
>
> but nothing was released ... also where do you put the specify the
> argument ? into mvn -Darguments="..." or outside mvn -Darguments="..." ?
>
> -----Message d'origine-----
> De : Francesco Mari [mailto:mari.france...@gmail.com]
> Envoyé : mardi 23 juillet 2013 11:49
> À : Maven Users List
> Objet : Re: release prepare with git doesn't finish
>
> The release:prepare goal has a password parameter which you can use from
> the command line [1].
>
> [1]:
>
> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#password
>
>
> 2013/7/23 Adrien Ruffié <adriennolar...@hotmail.fr>
>
> > Ok I have try without batch mode (on windows) and I have try to run
> > the previous command before it block ...
> >
> > "git push ssh://git@rd1/myapp.git release/Spring2013:release/Spring2013"
> >
> > and when I tried the following git line was prompt:
> > Enter passphrase for key '/c/Users/a.ruffie/.ssh/id_rsa':
> >
> >
> > After enter my passphrase the commit will be push correctly:
> >
> > Counting objects: 26, done.
> > Delta compression using up to 4 threads.
> > Compressing objects: 100% (15/15), done.
> > Writing objects: 100% (18/18), 327.80 KiB | 0 bytes/s, done.
> > Total 18 (delta 13), reused 4 (delta 3) To ssh://git@rd1/myapp.git
> >    200c7f1..3f5cd17  release/Spring2013 -> release/Spring2013
> >
> >
> > So I suppose the commit of "git push ssh://git@rd1/myapp.git
> > release/Spring2013:release/Spring2013" remains idle because the
> passphrase
> > cannot be provided.
> > Do you not a means to avoid this problem ?
> >
> > Like provide passphrase into maven command line ? like ....
> > release:perform -Dgit.password=mypassword
> >
> > Great thank and best regards.
> >
> > Adrien
> >
> > -----Message d'origine-----
> > De : Francesco Mari [mailto:mari.france...@gmail.com]
> > Envoyé : mardi 23 juillet 2013 10:54
> > À : Maven Users List
> > Objet : Re: release prepare with git doesn't finish
> >
> > I had a lot of issues using Git on Windows, especially combined with the
> > Maven Release Plugin. It looks like that the issue is related to long
> path
> > names.
> >
> > It may be that your project has long nested paths (usually Java
> > applications have this problem). Try to move your project to a shorter
> > path, e.g. C:\prj. This will not fix the issue, but it works sometimes.
> >
> > By the way, I use a Linux VM to release stuff. Working on Windows is sad,
> > overall.
> >
> >
> > 2013/7/23 Baptiste MATHUS <m...@batmat.net>
> >
> > > Hi,
> > > Try not running in non batch mode to maybe get the message of what is
> > > being waited for.
> > >
> > > I also see you're running git on windows. That might be part of the
> > > issue, so also double check you use the latest maven-release-plugin
> > version.
> > >
> > > cheers
> > > Le 23 juil. 2013 10:04, "Adrien Ruffié" <adriennolar...@hotmail.fr> a
> > > écrit :
> > >
> > > > Hello all I have a small problem,****
> > > >
> > > > ** **
> > > >
> > > > I try to release a branch version of my project with following
> > > > command
> > > (-X
> > > > is for debug only):****
> > > >
> > > > ** **
> > > >
> > > > Mvn -Darguments="-Dmaven.test.skip=true -Pdistribution-packaging"
> > > > release:prepare --batch-mode -Dtag=Spring2013/005
> > > > -DreleaseVersion=Spring2013-005
> > > > -DdevelopmentVersion=Spring2013-006-SNAPSHOT –X****
> > > >
> > > > ** **
> > > >
> > > > but the background processes hang indefinitely on the last line of
> > > > the
> > > log
> > > > file and I do not know why he did not direct, because the shots I
> > > > did not get a release: perform****
> > > >
> > > > ** **
> > > >
> > > > Do you have an idea why the process block/lock over  ?****
> > > >
> > > > ** **
> > > >
> > > > [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> > > > C:\Users\A9532~1.RUF\AppData\Local\Temp\maven-scm-1142711596.commit
> > > pom.xml
> > > > myapp-webapp\pom.xml myapp-install-wizard\pom.xml"****
> > > >
> > > > [INFO] Working directory: C:\Java\Workspaces\Indigo\myappcrm5****
> > > >
> > > > [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"****
> > > >
> > > > [INFO] Working directory: C:\Java\Workspaces\Indigo\myappcrm5****
> > > >
> > > > [INFO] Executing: cmd.exe /X /C "git push ssh://git@rd1/myappcrm.git
> > > > release/Spring2013:release/Spring2013"****
> > > >
> > > > ** **
> > > >
> > > > Great thank and best regards.****
> > > >
> > > > ** **
> > > >
> > > > Adrien****
> > > >
> > > >
> > > > --------------------------------------------------------------------
> > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: users-h...@maven.apache.org
> > > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to