[
https://issues.apache.org/jira/browse/MDEPLOY-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108048#comment-17108048
]
Olivier Lamy edited comment on MDEPLOY-267 at 5/15/20, 7:52 AM:
----------------------------------------------------------------
[~rfscholte] nobody says it's a Maven issue, It's just a new feature to help
users :)
was (Author: olamy):
[~rfscholte] nobody says it's a Maven issue, It's jus a new feature to help
users :)
> add parameters to deploy or not non snapshots or release (-DskipRelease or
> -DskipSnapshot)
> ------------------------------------------------------------------------------------------
>
> 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
>
>
> maven-release-plugin creates a commit where the pom is not a SNAPSHOT
> version: if CI system is configured to build on every commit and to deploy
> the artifacts on every build (with the intent in general to deploy updated
> SNAPSHOTs on every commit), the CI will deploy the non-SNAPSHOT that has
> already been deployed by the user who launched {{mvn release:perform}}, then
> it will generate an error (trying to override existing release artifact)
> and/or create new staging repository and/or override artifacts partially (if
> repository not configured to block overrides)
> we can add a new parameter {{-DdeployOnlySnaphots=true/false}}: it will be
> false per default for normal use, but can be configured to true in users' CI
> system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
