[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048028#comment-17048028
]
Olivier Lamy commented on MDEPLOY-267:
--------------------------------------
If you use a pattern such releasing from master because of the
maven-release-plugin master can have a non SNAPSHOT version.
why a hack? how do you want to prevent deploying non SNAPSHOT without having
build failure and you cannot do anything to prevent this.
I have less concern install/local repo CI builds can easily cleanup local repo
and now with cloud agent they mostly start with an empty repo.
> add a parameter to not deploy non snapshots (-DdeployOnlySnaphots=true/false)
> -----------------------------------------------------------------------------
>
> Key: MDEPLOY-267
> URL: https://issues.apache.org/jira/browse/MDEPLOY-267
> Project: Maven Deploy Plugin
> Issue Type: New Feature
> Reporter: Olivier Lamy
> Assignee: Olivier Lamy
> Priority: Major
> Fix For: 3.0.0
>
>
> in case of maven-release-plugin it happen the pom contains non SNAPSHOT
> version and so CI system try to deploy the artifacts this can generate an
> error and/or create new staging repository
> we can add a new parameter -DdeployOnlySnaphots=true/false. For backward
> compat it will be false per default but users will be able to configure their
> CI system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
