[jira] Created: (SCM-443) login failure
login failure - Key: SCM-443 URL: http://jira.codehaus.org/browse/SCM-443 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Affects Versions: 1.1.1 Environment: windows service Java(TM) SE Runtime Environment (build 1.6.0_12-b04) with continnum in standalone mode perforce 2008.2 security level 3 Reporter: Raphael PETIT Priority: Blocker Index: PerforceLoginCommand.java === --- PerforceLoginCommand.java (revision 750811) +++ PerforceLoginCommand.java (working copy) @@ -69,7 +69,7 @@ int exitCode = CommandLineUtils.executeCommandLine( cl, new StringBufferInputStream(password), consumer, err ); isSuccess = consumer.isSuccess(); -if ( isSuccess ) +if (! isSuccess ) { String cmdLine = CommandLineUtils.toString( cl.getCommandline() ); -- 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] Commented: (SCM-292) Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in memory clientspec names
[ http://jira.codehaus.org/browse/SCM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94674 ] Raphael PETIT commented on SCM-292: --- Currently, each client spec has - a root with the unique number at the end - a view defined by one line Maybe, it can be changed to a unique client spec - a root (global definition) - a view defined by several line the unique number at the end So things seems to be manageable without continnum concept in the scm... > Replace DEFAULT_CLIENTSPEC_PROPERTY system property by a map to store in > memory clientspec names > > > Key: SCM-292 > URL: http://jira.codehaus.org/browse/SCM-292 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-perforce >Affects Versions: 1.0-beta-4 >Reporter: Emmanuel Venisse >Assignee: Patrick Schneider >Priority: Critical > Fix For: 1.0 > > > With a Map instead of a system property, we'll can support more that one > clientspec in the jvm. It's necessary for Continuum because it access to more > than one project in Perforce. -- 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-301) perforce cannot be used with continuum
perforce cannot be used with continuum -- Key: SCM-301 URL: http://jira.codehaus.org/browse/SCM-301 Project: Maven SCM Issue Type: Bug Affects Versions: 1.0-rc1 Environment: summary 1- fix nullpointer in changelog command 2- add logger 3- client is no more a mandatory field in accept in the perforceInfoCommand (constraint not usefull because scm create new ones) 4- add workaround (due to continuum) to accept the default choice instead of null or empty string 5- ignore pom.xml contains if the the location is not in client spec (link to 3) Reporter: Raphael PETIT Attachments: perforce.patch -- 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