[ https://issues.apache.org/jira/browse/MDEPLOY-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841032#comment-16841032 ]
Karl Heinz Marbaise commented on MDEPLOY-250: --------------------------------------------- For version 3.X {{ -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'}} has to be {{ -DaltDeploymentRepository=snapshot-repo::file:./local-snapshots-dir clean deploy'}} > add documentation on managing network issues > -------------------------------------------- > > Key: MDEPLOY-250 > URL: https://issues.apache.org/jira/browse/MDEPLOY-250 > Project: Maven Deploy Plugin > Issue Type: Task > Components: deploy:deploy > Affects Versions: 3.0.0-M1 > Reporter: Hervé Boutemy > Priority: Major > Fix For: 3.0.0 > > > network issues are happening sometimes, then there are strategies that have > been found to workaround, from simple retries, to 2-steps deploy through > local staging, like done by plc4x: > see in [https://github.com/apache/incubator-plc4x/blob/develop/Jenkinsfile]: > {noformat} > // We'll deploy to a relative directory so we can save > // that and deploy in a later step on a different node > sh 'mvn -P${JENKINS_PROFILE},development ${MVN_TEST_FAIL_IGNORE} > ${JQASSISTANT_NEO4J_VERSION} > -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir > clean deploy' > {noformat} > followed by: > {noformat} > // Deploy the artifacts using the wagon-maven-plugin. > sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload' > {noformat} > sharing such strategy can be useful to many -- This message was sent by Atlassian JIRA (v7.6.3#76005)