[jira] Commented: (SCM-114) Clientspec naming

2005-12-15 Thread mike perham (JIRA) 
[ http://jira.codehaus.org/browse/SCM-114?page=comments#action_53488 ] 

mike perham commented on SCM-114:
-

The Perforce plugin will NOT obey P4CLIENT because it needs to support multiple 
clientspecs with Continuum.  It will NOT obey P4PASSWD because it does not do 
any security.  It assumes the p4 user is already logged in.  When I tried to 
handle users and passwords, I ran into nothing but problems so I punted on that 
whole aspect.

 Clientspec naming
 -

  Key: SCM-114
  URL: http://jira.codehaus.org/browse/SCM-114
  Project: Maven SCM
 Type: Improvement

   Components: maven-scm-provider-perforce
 Versions: 1.0-beta-3
 Reporter: mike perham
  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 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

[jira] Assigned: (SCM-108) JDK 1.5 code

2005-12-15 Thread Dan Tran (JIRA) 
 [ http://jira.codehaus.org/browse/SCM-108?page=all ]

Dan Tran reassigned SCM-108:


Assign To: Dan Tran

 JDK 1.5 code
 

  Key: SCM-108
  URL: http://jira.codehaus.org/browse/SCM-108
  Project: Maven SCM
 Type: Bug

   Components: maven-scm-provider-clearcase
 Reporter: mike perham
 Assignee: Dan Tran
  Attachments: clearcase-108.patch


 [INFO] Compilation failure
 D:\apache\maven-scm\maven-scm-providers\maven-scm-provider-clearcase\src\main\java\org\apache\maven\
 scm\provider\clearcase\repository\ClearCaseScmProviderRepository.java:[113,31]
  cannot resolve symbol
 symbol  : method toURI ()
 location: class java.net.URL

-- 
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

[jira] Created: (SCM-117) Add parameters to scm configuration element

2005-12-15 Thread Aviran Mordo (JIRA) 
Add parameters to scm configuration element
---

 Key: SCM-117
 URL: http://jira.codehaus.org/browse/SCM-117
 Project: Maven SCM
Type: Wish

Reporter: Aviran Mordo


It would be very nice to have the ability to add parameters to the scm element. 
For instance to add parameter to always force checkout. for instance in 
Starteam I would like to add -o so every time stcmd is called the parameters 
will be concatenated to the command line

-- 
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