release prepare with git doesn't finish
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
AW: mvn release:prepare does not update parent version
Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-interactive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg k...@quipsy.de wrote: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse - 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
Re: mvn release:prepare does not update parent version
The example you mention updates the build artifacts only. When you release code, you would of course assign a version number to the release, and you can specify what snapshot version you want to use next. That makes the release consistent with all of the tests. It's simple labeling what is being released. Changing the version number of outside artifacts that you reference, on the other hand, is a change in the definition and functionality of the system. There is no particular reason to expect it to work, and more than if you decided to ask Maven to modify any other code in your system. Russ On Jul 23, 2013, at 4:10 AM, christofer.d...@c-ware.de wrote: Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-interactive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg k...@quipsy.de wrote: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse - 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 - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html!
RE: mvn release:prepare does not update parent version
So this is a known bug or is it just a configuration error that I did? I have to specify all versions of each module of my reactor? Or it can take the basic version-DreleaseVersion for each module? -Message d'origine- De : christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Envoyé : mardi 23 juillet 2013 10:10 À : Maven Users List Objet : AW: mvn release:prepare does not update parent version Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-inte ractive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg k...@quipsy.de wrote: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse - 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
Re: release prepare with git doesn't finish
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
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
RE: release prepare with git doesn't finish
Ok great thank all, I first try without batch mode, but normally it's my Jenkins (on ubutun) which is supposed to release this job ... I try on jenkins and without batch mode and coming back to you later. Thank :-) -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
RE: release prepare with git doesn't finish
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
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
Re: release prepare with git doesn't finish
Alternatively you could use 'ssh-add' (the most secure option IMO) before releasing or use a ssh key without password. On Tue, Jul 23, 2013 at 11:49 AM, Francesco Mari mari.france...@gmail.comwrote: 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 -- Adrien Rivard
RE: release prepare with git doesn't finish
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
Re: release prepare with git doesn't finish
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 ** **
Re:Re:Error of after running 'mvn package' command
Can you guys help me resolve it , my own project totally block by this problem. Thanks. At 2013-07-23 09:18:50,邹志勇 zouzhiyong0...@163.com wrote: Thanks, when i invoke the command ' ls -al /home/zouzy/.m2 ' , it is the directory of repository, not have the file of setting.xml .
AW: mvn release:prepare does not update parent version
You don't get my point. My problem is that the plugin asks me to provide the version to set for the parentversion tag, but it actually does not use it. This is what I complain about, solely. I don't want to update anything else. -Ursprüngliche Nachricht- Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Gesendet: Dienstag, 23. Juli 2013 10:10 An: Maven Users List Betreff: AW: mvn release:prepare does not update parent version Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-interactive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg k...@quipsy.de wrote: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse - 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
AW: mvn release:prepare does not update parent version
But why is release:prepare explicitly asking me whether I want to update that number and what that number is, when it is intended behaviour that it does not actually set that number into the POM? I would understand all what you say if the plugin would not ask for the next development version of parent. But it DOES ask. -Ursprüngliche Nachricht- Von: Russell Gold [mailto:r...@gold-family.us] Gesendet: Dienstag, 23. Juli 2013 10:27 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version The example you mention updates the build artifacts only. When you release code, you would of course assign a version number to the release, and you can specify what snapshot version you want to use next. That makes the release consistent with all of the tests. It's simple labeling what is being released. Changing the version number of outside artifacts that you reference, on the other hand, is a change in the definition and functionality of the system. There is no particular reason to expect it to work, and more than if you decided to ask Maven to modify any other code in your system. Russ On Jul 23, 2013, at 4:10 AM, christofer.d...@c-ware.de wrote: Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here: http://maven.apache.org/maven-release/maven-release-plugin/examples/no n-interactive-release.html It is possible to provide separate versions for every module. In my release I provided release and development versions for all modules (also ones not in the reactor), but the release:prepare simply skipped those not in the build. I had to create a patched version for this, but it was a pretty unsatisfying solution. If the plugin would for example update all those versions in the reactor plus all those I manually provided a version for, might solve Markus' problems. Chris -Ursprüngliche Nachricht- Von: jieryn [mailto:jie...@gmail.com] Gesendet: Montag, 22. Juli 2013 20:36 An: Maven Users List Betreff: Re: mvn release:prepare does not update parent version Greetings, On Mon, Jul 22, 2013 at 8:25 AM, Markus Karg k...@quipsy.de wrote: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I don't think the language says that at all. I ran a quick build and I'm not seeing where it says it will update every single SNAPSHOT version referenced in the POM. Can you please paste it? I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. And it should not. It will rewrite the versions for the artifacts in its build plan, and the parent is not part of the build plan in this way. It would be horrifying, frankly, if running a release in a project would go update the parent project also. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. I don't think it should obviously do that. Perhaps you actually intended to run the release from the parent, if that is true, then you should do it from there. Not from within some submodule. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Run the release from the proper location. Or if the parent really does not have a submodule of the project you're errantly trying to run the release from right now, then you should release it (parent) first and then make the updates in the unlinked child projects to the latest release number. The m-versions-p is quite adept at automating this process. -Jesse - 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 - Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.gold-family.us/audio/misfile.html! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: release prepare with git doesn't finish
Operation does not work very well ... C:\Java\Workspaces\Indigo\myappcrm5mvn -Darguments=-Dmaven.test.skip=true -Pdistribution-packaging release:prepare release:perform -Dtag=Spring2013 /005 -Dcom.myapp.frontline:myapp-webapp=Spring2013/005 -Dcom.myapp.frontline:myapp-install-wizard=Spring2013/005 -DreleaseVersion=Spring2013-005 -Ddev elopmentVersion=Spring2013-006-SNAPSHOT -Dpassword=mypassword -X it try to push with following url git push ssh://git:mypassword@rd1/myapp.git release/Spring2013:release/Spring2013 I think it confuses the password with the login ... therefore the url does not work -Message d'origine- De : Francesco Mari [mailto:mari.france...@gmail.com] Envoyé : mardi 23 juillet 2013 12:17 À : Maven Users List Objet : Re: release prepare with git doesn't finish 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-moj o.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
Re: release prepare with git doesn't finish
Try to use -Dusername to specify a user name, too. 2013/7/23 Adrien Ruffié adriennolar...@hotmail.fr Operation does not work very well ... C:\Java\Workspaces\Indigo\myappcrm5mvn -Darguments=-Dmaven.test.skip=true -Pdistribution-packaging release:prepare release:perform -Dtag=Spring2013 /005 -Dcom.myapp.frontline:myapp-webapp=Spring2013/005 -Dcom.myapp.frontline:myapp-install-wizard=Spring2013/005 -DreleaseVersion=Spring2013-005 -Ddev elopmentVersion=Spring2013-006-SNAPSHOT -Dpassword=mypassword -X it try to push with following url git push ssh://git:mypassword@rd1/myapp.git release/Spring2013:release/Spring2013 I think it confuses the password with the login ... therefore the url does not work -Message d'origine- De : Francesco Mari [mailto:mari.france...@gmail.com] Envoyé : mardi 23 juillet 2013 12:17 À : Maven Users List Objet : Re: release prepare with git doesn't finish 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-moj o.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
Re: Error of after running 'mvn package' command
Did you put a setting.xml file there? Just put one there based on what is written http://maven.apache.org/settings.html Ron On 23/07/2013 7:10 AM, 邹志勇 wrote: Can you guys help me resolve it , my own project totally block by this problem. Thanks. At 2013-07-23 09:18:50,邹志勇 zouzhiyong0...@163.com wrote: Thanks, when i invoke the command ' ls -al /home/zouzy/.m2 ' , it is the directory of repository, not have the file of setting.xml . -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn release:prepare does not update parent version
Greetings, On Tue, Jul 23, 2013 at 7:45 AM, Markus Karg k...@quipsy.de wrote: But why is release:prepare explicitly asking me whether I want to update that number and what that number is, when it is intended behaviour that it does not actually set that number into the POM? I would understand all what you say if the plugin would not ask for the next development version of parent. But it DOES ask. Ok, that is definitely odd. Can you please provide a minimal project which reproduces that issue? -Jesse - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: release prepare with git doesn't finish
Same thing maven chain parameter like ssh://git:adryen31:mypassword@rd1/myapp.git Just stupid parameters I think ... -Message d'origine- De : Francesco Mari [mailto:mari.france...@gmail.com] Envoyé : mardi 23 juillet 2013 14:02 À : Maven Users List Objet : Re: release prepare with git doesn't finish Try to use -Dusername to specify a user name, too. 2013/7/23 Adrien Ruffié adriennolar...@hotmail.fr Operation does not work very well ... C:\Java\Workspaces\Indigo\myappcrm5mvn -Darguments=-Dmaven.test.skip=true -Pdistribution-packaging release:prepare release:perform -Dtag=Spring2013 /005 -Dcom.myapp.frontline:myapp-webapp=Spring2013/005 -Dcom.myapp.frontline:myapp-install-wizard=Spring2013/005 -DreleaseVersion=Spring2013-005 -Ddev elopmentVersion=Spring2013-006-SNAPSHOT -Dpassword=mypassword -X it try to push with following url git push ssh://git:mypassword@rd1/myapp.git release/Spring2013:release/Spring2013 I think it confuses the password with the login ... therefore the url does not work -Message d'origine- De : Francesco Mari [mailto:mari.france...@gmail.com] Envoyé : mardi 23 juillet 2013 12:17 À : Maven Users List Objet : Re: release prepare with git doesn't finish 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-m oj o.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
[RESULT] [VOTE] Retire maven-idea-plugin
Hi, The vote has passed with the following result: +1 (binding): Arnaud Héritier, Robert Scholte, Stéphane Nicoll, Ralph Goers, Stephen Connolly, Olivier Lamy, Kristian Rosenvold, Wayne Fay, Brett Porter, Dennis Lundberg +1 (non binding): Lennart Jörelid, Anders Hammar, Baptiste Mathus, Chris Graham I will continue with the steps required to retire this plugin. On Fri, Jul 19, 2013 at 7:01 PM, Dennis Lundberg denn...@apache.org wrote: Hi It has been almost five years since I made the last release of maven-idea-plugin. The features in IDEA to integrate Maven has been greatly improved since then, making our own plugin obsolete. I therefor propose that we retire maven-idea-plugin. If this vote is successful I will make one final release of the plugin, making it clear on the plugin site that it has been retired. After that the source code will be moved into the retired area in Subversion. This is AFAIK the first vote to follow our process for retiring a plugin. For those interested, the process is described here: http://maven.apache.org/developers/retirement-plan-plugins.html [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire Maven Model Converter
Hi, The vote has passed with the following result: +1 (binding): Arnaud Héritier, Hervé Boutemy, Wayne Fay, Stephen Connolly, Ralph Goers, Brett Porter, Dennis Lundberg +1 (non binding): Lennart Jörelid, Baptiste Mathus I will continue with the steps required to retire this shared component. On Sat, Jul 20, 2013 at 7:26 PM, Dennis Lundberg denn...@apache.org wrote: Hi, The only consumer of Maven Model Converter we have left at the Apache Maven project is Maven One Plugin. If the vote for the retirement of Maven One Plugin succeeds we should also retire Maven Model Converter. The last release was made almost six years ago. Last time I checked Maven Model Converter was also used by the Apache Archiva project. The retirement plan is to move the component to the Apache Archiva project, if they want it. http://maven.apache.org/shared/maven-model-converter/ I therefor propose that we retire maven-model-converter. If this vote is successful I will make one final release of the component (there are some issues that have been fixed) making it clear on the component site that it has been retired. After that the source code will be moved to the Apache Archiva project in Subversion, or if they do not want it to the retired area in Subversion. The process for retiring a plugin is described here: http://maven.apache.org/developers/retirement-plan-plugins.html The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Retire Maven One Plugin
Hi, The vote has passed with the following result: +1 (binding): Olivier Lamy, Robert Scholte, Arnaud Héritier, Hervé Boutemy, Wayne Fay, Stephen Connolly, Ralph Goers, Brett Porter, Stephane Nicoll, Dennis Lundberg +1 (non binding): Anders Hammar, Lennart Jörelid, Baptiste Mathus I will continue with the steps required to retire this plugin. On Sat, Jul 20, 2013 at 11:13 AM, Dennis Lundberg denn...@apache.org wrote: Hi, Now that we have Maven 1 at End-Of-Life, I think it's time to retire Maven One Plugin as well. It has been almost six years since the last release. I therefor propose that we retire maven-one-plugin. http://maven.apache.org/plugins/maven-one-plugin/ If this vote is successful I will make one final release of the plugin, making it clear on the plugin site that it has been retired. After that the source code will be moved into the retired area in Subversion. The process for retiring a plugin is described here, and is being improved: http://maven.apache.org/developers/retirement-plan-plugins.html The vote is open for 72 hours. [ ] +1 Yes, it's about time [ ] -1 No, because... -- Dennis Lundberg -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: mvn release:prepare does not update parent version
Markus Parent.pom | v - | | v v Child1.pom Child2.pom release:prepare where property updates/changes Child1.pom Child11.pom Child12.pom | v --- | | v v Child11.pom Child12.pom can you envision a scenario where release plugin should break inheritance and update Parent instead of child module s ? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Subject: RE: mvn release:prepare does not update parent version Date: Mon, 22 Jul 2013 22:29:07 +0200 From: k...@quipsy.de To: users@maven.apache.org Thanks for picking up this thread! I am using: Maven 3.0.4 and maven-release-plugin 2.4.1 -Markus Hi, which version of Maven and Maven-Release-Plugin are you using? On Mon, Jul 22, 2013 at 9:25 AM, Markus Karg k...@quipsy.de wrote: I'm driving nuts with mvn release:prepare...: When I do mvn release:prepare, Maven asks whether I want to update all SNAPSHOT version referenced in the POM. I say yes and confirm all suggested replacement versions unchanged. When Maven is done, I check the POM.xml. It is correctly rewritten for all references, but not for the parent version. The parent version still references the *old* SNAPSHOT, while obviously it should now name the *next* SNAPSHOT. Can somebody tell me what I have to do so that mvn release:prepare will also make the parent version point tot he *next* SNAPSHOT, as it does it correctly with the dependencies and the project's own version? Thanks! -Markus - 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
maven surefire - selecting providers
Hello all, we have maven builds for projects that use both jUnit and testNG tests. So I configured the maven surefire plugin to use multiple providers ( http://maven.apache.org/surefire/maven-surefire-plugin/examples/providers.html) and it works pretty well - apart from the problem, that now TestNG tries to run every single jUnit test in the project. It takes about 2 seconds for each test until it finds out that it has nothing to to (only jUnit annotations on the test class) The annoying part is that now some tests that failed with jUnit are marked ok after TestNG didn't find a problem. Is there anyway to configure surefire or the providers so that they only run their own tests and ignore the others? A solution where rename the test to filter by names would be fine for me. Best regards, Andreas
RE: ForkedBooter in 2.2.1 does not honor MAVEN_OPTS
Ben the reason why i always set forkMode to 'never' in my pom executing maven-surefire-plugin properties forkModenever/forkMode /properties -Djava.awt.headless=true directive *presumes* you are running awt GUI yet Iam not seeing any reference for java.awt in maven-surefire-plugin src (2.2.1 is at least 5 years old and has been deprecated ) other than political...is there any cogent reason NOT to upgrade surefire to AT LEAST 2.4.2 ? Martin __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: vincent.lato...@gmail.com Date: Mon, 22 Jul 2013 07:57:26 +0200 Subject: Re: ForkedBooter in 2.2.1 does not honor MAVEN_OPTS To: users@maven.apache.org Hello, This is the JVM forked to execute unit tests (through maven-surefire-plugin). Check [1] to set options for that jvm. [1] http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#argLine Vincent 2013/7/20 Ben Siemon ben.sie...@opower.com Specifically I have -Djava.awt.headless=true set in my maven options. Other surefire booters seem to honor the headless mode and not steal focus but the ForkedBooter still steals focus even when headless is set to true in MAVEN_OPTS. Running jps -v yields this view of the two maven jvms started: Parent Maven with the correct MAVNE_OPTS 29028 Launcher -Xms2048m -Xmx4096m -XX:PermSize=1024m -XX:MaxPermSize=2048m -Djava.awt.headless=true -Dclassworlds.conf=/usr/local/apache-maven//bin/m2.conf -Dmaven.home=/usr/local/apache-maven/ ForkedBooter without the maven opts. This process steals my screen each time it runs. 29033 surefirebooter3016997434240550753.jar -XX:+HeapDumpOnOutOfMemoryError -Xmx512M -XX:MaxPermSize=128M maven version: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400) Java version: 1.6.0_51 Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x version: 10.8.4 arch: x86_64 Family: mac Upgrading from this version is not currently possible. I am not sure why mvn is now using this forked booter in place of the earlier one that honored MAVEN_OPTS. It might be that upstream changes in parent artifacts are forcing me to run the ForkedBooter instead. Thanks for any help you can offer. -- *Ben Siemon* Senior Software Engineer, Engineering *Opower* http://www.opower.com We’re hiring! See jobs here http://www.opower.com/careers.
RE: chaining release:prepare release:perform for multi-module [I]
you can specify which goals to execute before the release to quote goalsA space separated list of goals to execute on deployment. Default value is either deploy or deploy site-deploy, if the project has a distributionManagement/site element. User property is: goals. /goals http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. To: users@maven.apache.org Subject: chaining release:prepare release:perform for multi-module [I] From: nathan.co...@db.com Date: Thu, 18 Jul 2013 16:23:17 +0100 Classification: For internal use only Hi all, I appreciate the normal approach to executing a maven release is to execute release:prepare, followed by release:perform I am attempting to set up a release job within our build server (TeamCity) which will atomically create a release. Assuming successful execution. mvn release:prepare release:perform My concern is that this will execute prepare followed by perform upon each module in the reactor build order. Where what is needed is for release:prepare to be executed in full, followed by release perform in full. Is there any way to configure this in a single chained command? Or will I have to configure multiple build jobs and link the jobs? Regards, Nathan --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
