[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MDEPLOY-267:
----------------------------------
Description:
in case of maven-release-plugin, it happens 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.
was:
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.
> 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 happens 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)
