[
https://issues.apache.org/jira/browse/SCM-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961440#comment-17961440
]
ASF GitHub Bot commented on SCM-429:
------------------------------------
jira-importer opened a new issue, #643:
URL: https://github.com/apache/maven-scm/issues/643
**[Markus
Umefjord](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=umefjord)**
opened
**[SCM-429](https://issues.apache.org/jira/browse/SCM-429?redirect=false)** and
commented
The clearcase provider has no support for creating releases in branches,
i.e. user defined config specs.
mvn release:perform
fails with the message "Building on a label not supported with
user-specified config specs". Release:prepare does it's job just fine, and
release:perform creates the clearcase label, updates the pom etc, but fails to
create a new view that it can build from. This shouldn't be too hard to
implement given that a temporary config spec could look like:
element * MY_LABEL
load \project1
load \project2
...
Given that the load rules are copied from the originating config spec.
---
**Affects:** 1.1
3 votes, 4 watchers
> Add release support for branches (user defined config specs)
> ------------------------------------------------------------
>
> Key: SCM-429
> URL: https://issues.apache.org/jira/browse/SCM-429
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.1
> Environment: Win XP, Maven 2.0.9, Clearcase 2003.06.00
> Reporter: Markus Umefjord
> Priority: Critical
>
> The clearcase provider has no support for creating releases in branches, i.e.
> user defined config specs.
> mvn release:perform
> fails with the message "Building on a label not supported with user-specified
> config specs". Release:prepare does it's job just fine, and release:perform
> creates the clearcase label, updates the pom etc, but fails to create a new
> view that it can build from. This shouldn't be too hard to implement given
> that a temporary config spec could look like:
> element * MY_LABEL
> load \project1
> load \project2
> ...
> Given that the load rules are copied from the originating config spec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
