[
https://issues.apache.org/jira/browse/SCM-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964315#comment-17964315
]
Olivier Lamy commented on SCM-114:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#381|https://github.com/apache/maven-scm/issues/381].
> Clientspec naming
> -----------------
>
> Key: SCM-114
> URL: https://issues.apache.org/jira/browse/SCM-114
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> 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
>
>
> Several people have expressed more than a passing interest in how the
> Perforce clientspec is named by Maven SCM. The name needs to be
> autogenerated and unique for each Continuum project build. Currently I am
> thinking something like:
> ${project}-${user}-${hostname}-mavenscm
> Emmannuel, does the SCM subsystem have access to the name of the project
> being built? If not, I can just use the name of the last directory in the
> SCM URL for the name of the project: //depot/projects/foobar would mean that
> ${project} = foobar.
> And just head off the inevitable question: you cannot set P4CLIENT for this
> because Continuum may build several different projects and they each need a
> unique clientspec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
