[
https://issues.apache.org/jira/browse/SCM-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964883#comment-17964883
]
Olivier Lamy commented on SCM-654:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#862|https://github.com/apache/maven-scm/issues/862].
> Use of release plugin impossible when change package mandatory policy
> activated on integrity server
> ---------------------------------------------------------------------------------------------------
>
> Key: SCM-654
> URL: https://issues.apache.org/jira/browse/SCM-654
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-integrity
> Affects Versions: 1.6
> Environment: Maven 2.2.1
> Java 1.6.0_11
> Windows XP
> MKS Source 2009
> Build: 8.10.0.5799
> Service Pack: 005-01
> Hotfixes: C041000005-019, C041000005-021
> Copyright 2001 - 2010 MKS Software Inc.; in Canada copyright owned by MKS
> Inc. All rights reserved.
> Reporter: Jeremie BOUSQUET
> Priority: Major
> Attachments: IntegrityCM-Maven-Plugin.docx
>
>
> Trying to use the release plugin with the "integrity" provider.
> Problem is that if "Change Package Mandatory" policy is activated, the
> release plugin can't commit changes in SCM, because SCM modification commands
> (edit, add, ...) do not create change package(s).
> I think to support this kind of configuration, there could be a change
> package creation on add, edit and lock commands, a discard CP on unedit, and
> a submit CP on checkin, or something like that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
