You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by "mike perham (JIRA)" <ji...@codehaus.org> on 2005/12/20 16:17:35 UTC
[jira] Assigned: (SCM-113) Support persistent and transient
clientspecs
[ http://jira.codehaus.org/browse/SCM-113?page=all ]
mike perham reassigned SCM-113:
-------------------------------
Assign To: mike perham
> Support persistent and transient clientspecs
> --------------------------------------------
>
> Key: SCM-113
> URL: http://jira.codehaus.org/browse/SCM-113
> Project: Maven SCM
> Type: New Feature
> Components: maven-scm-provider-perforce
> Versions: 1.0-beta-3
> Reporter: mike perham
> Assignee: mike perham
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira