[
https://issues.apache.org/jira/browse/SCM-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960422#comment-17960422
]
ASF GitHub Bot commented on SCM-113:
------------------------------------
jira-importer commented on issue #400:
URL: https://github.com/apache/maven-scm/issues/400#issuecomment-2964591870
**[Wim
Deblauwe](https://issues.apache.org/jira/secure/[email protected])**
commented
For ClearCase, we only support what you call a persistent clientspec. The
scm url points to the location of the spec on some server. The release:perform
part of the release plugin is currently not supported for clearcase. We would
need something like the transient spec you talk about.
> Support persistent and transient clientspecs
> --------------------------------------------
>
> Key: SCM-113
> URL: https://issues.apache.org/jira/browse/SCM-113
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Reporter: Mike Perham
> Assignee: Mike Perham
> Priority: Major
> Fix For: 1.0-beta-3
>
>
> Continuum needs a persistent clientspec because it needs to update a
> project's source code and build it once an hour. On larger projects a
> complete resync might take 10-20 minutes so it is necessary to keep a
> clientspec around for that Continuum project build so syncs only take a few
> seconds.
> However, the Maven Release plugin may need to be used by tens or even
> hundreds of developers to release any number of small modules. Currently
> this would mean lots of clientspecs being created for the release checkout
> which are reused very infrequently. Here I would prefer to create the
> clientspec, do the checkout, build and then delete the clientspec. This is
> what I term a transient clientspec.
> The Perforce plugin would need to default to one mode and support some sort
> of hint which tells it which mode to operate in.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
