[jira] Commented: (MDEPLOY-46) mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber
[ http://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=233858#action_233858 ] Maria Odea Ching commented on MDEPLOY-46: - This seems to be fixed in 2.5. Please verify so we can close this issue. mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber -- Key: MDEPLOY-46 URL: http://jira.codehaus.org/browse/MDEPLOY-46 Project: Maven 2.x Deploy Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Geoffrey De Smet Attachments: MDEPLOY-46.patch I 've checkouted a m2 project (spring-richclient) and deployed it to my local repo using the altDeploymentRepository parameter (from MDEPLOY-41). But the checkout is a SNAPSHOT version and the deployer should replace it with something like spring-richclient-core-0.3.0-20070101.160450-2.jar like the mvn deploy without altDeploymentRepository does, but it doesn't: [INFO] [deploy:deploy] altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Using alternate deployment repository ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Retrieving previous build number from ggg-dev Uploading: scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar 50K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEPLOY-46) mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber
[ http://jira.codehaus.org/browse/MDEPLOY-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95880 ] Geoffrey De Smet commented on MDEPLOY-46: - Even setting -DupdateReleaseInfo=true doesn't help, try it yourself: mvn deploy -DaltDeploymentRepository=ggg-deploy::default::file:///D:/tmp/delete/repo/ -DupdateReleaseInfo=true mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber -- Key: MDEPLOY-46 URL: http://jira.codehaus.org/browse/MDEPLOY-46 Project: Maven 2.x Deploy Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Geoffrey De Smet I 've checkouted a m2 project (spring-richclient) and deployed it to my local repo using the altDeploymentRepository parameter (from MDEPLOY-41). But the checkout is a SNAPSHOT version and the deployer should replace it with something like spring-richclient-core-0.3.0-20070101.160450-2.jar like the mvn deploy without altDeploymentRepository does, but it doesn't: [INFO] [deploy:deploy] altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Using alternate deployment repository ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Retrieving previous build number from ggg-dev Uploading: scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar 50K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEPLOY-46) mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber
[ http://jira.codehaus.org/browse/MDEPLOY-46?page=comments#action_84022 ] Geoffrey De Smet commented on MDEPLOY-46: - One of the modules had NullPointerException in it, but according to WAGONSSH-49 that's an independend issue: [INFO] Using alternate deployment repository ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Retrieving previous build number from ggg-dev Uploading: scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient/0.3.0-SNAPSHOT/spring-richclient-0.3.0-SNAPSHOT.pom 37K uploaded Exception in thread Exec thread mvn.ggg.be java.lang.NullPointerException at com.jcraft.jsch.ChannelSession.run(Unknown Source) at java.lang.Thread.run(Thread.java:619) mvn -DaltDeploymentRepository=... deploy of a SNAPSHOT doesn't replace date.buildnumber -- Key: MDEPLOY-46 URL: http://jira.codehaus.org/browse/MDEPLOY-46 Project: Maven 2.x Deploy Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Geoffrey De Smet I 've checkouted a m2 project (spring-richclient) and deployed it to my local repo using the altDeploymentRepository parameter (from MDEPLOY-41). But the checkout is a SNAPSHOT version and the deployer should replace it with something like spring-richclient-core-0.3.0-20070101.160450-2.jar like the mvn deploy without altDeploymentRepository does, but it doesn't: [INFO] [deploy:deploy] altDeploymentRepository = ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Using alternate deployment repository ggg-dev::default::scp://mvn.ggg.be/maven/maven2/dev [INFO] Retrieving previous build number from ggg-dev Uploading: scp://mvn.ggg.be/maven/maven2/dev/org/springframework/richclient/spring-richclient-core/0.3.0-SNAPSHOT/spring-richclient-core-0.3.0-SNAPSHOT.jar 50K uploaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
