[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Code changed in jenkins User: Olivier Lamy Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/c074ac3cab43ba450ed69be6ba8610771a707396 Log: Merge pull request #28 from rwegmann/JENKINS-4861 JENKINS-4861: Fix post-build deployment of Maven artifacts with scpexe-type repository Compare: https://github.com/jenkinsci/maven-plugin/compare/4d1f9cc3014a...c074ac3cab43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon resolved JENKINS-4861 as Fixed Post-build deployment of Maven artifacts does not work with scpexe-type repository Change By: SCM/JIRA link daemon (25/Aug/14 5:33 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
SCM/JIRA link daemon commented on JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository Code changed in jenkins User: Raúl Wegmann Path: pom.xml http://jenkins-ci.org/commit/maven-plugin/7f6145d8faead72a999d69f9bed36d601b193508 Log: FIXED JENKINS-4861 Use newer version of transitive plexus-utils dependency that allows to correctly deploy artifacts using scpexe. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann updated JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository We are seeing this problem again when using any Jenkins version greater than 1.559 so that we have been stuck for the last few months with that version. Apparently some CLI escaping issues have been fixed in the plexus-utils library since version 3.0.10, which is the one included in the maven-plugin, and I believe that this bug may have been fixed since 3.0.16 (https://jira.codehaus.org/browse/PLXUTILS-161). Please consider including the changes of the following pull request that fixes this error by bumping the plexus-utils version to the most recent one (3.0.17): https://github.com/jenkinsci/maven-plugin/pull/28 Change By: Raúl Wegmann (22/Aug/14 4:30 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
