[jira] Updated: (SCM-19) resolve file status ambiguities
[ http://jira.codehaus.org/browse/SCM-19?page=all ] Torbjørn EIkli Smørgrav updated SCM-19: --- Attachment: MNG-19_1-maven-scm-api.patch > resolve file status ambiguities > --- > > Key: SCM-19 > URL: http://jira.codehaus.org/browse/SCM-19 > Project: Maven SCM > Type: Task > Components: maven-scm-api > Reporter: Brett Porter > Fix For: 1.0 > Attachments: MNG-19-maven-scm-api.patch, MNG-19_1-maven-scm-api.patch > > > currently ScmFileStatus just reports whatever the provider gave back, but > means different things in different SCM's. > eg. "updated" in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED. > "added" in CVS is UPDATED, in SVN it is ADDED. > The API should hide this from the user, though perhaps be able to give the > extended info if necessary. > I suggest isXXX flags instead: > isUpdated() > isAdded() - just came from an update > isMerged() > isInConflict() > isNew() - new locally > etc. -- 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] Updated: (SCM-19) resolve file status ambiguities
[ http://jira.codehaus.org/browse/SCM-19?page=all ] Torbjørn EIkli Smørgrav updated SCM-19: --- Attachment: MNG-19-maven-scm-api.patch > resolve file status ambiguities > --- > > Key: SCM-19 > URL: http://jira.codehaus.org/browse/SCM-19 > Project: Maven SCM > Type: Task > Components: maven-scm-api > Reporter: Brett Porter > Fix For: 1.0 > Attachments: MNG-19-maven-scm-api.patch > > > currently ScmFileStatus just reports whatever the provider gave back, but > means different things in different SCM's. > eg. "updated" in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED. > "added" in CVS is UPDATED, in SVN it is ADDED. > The API should hide this from the user, though perhaps be able to give the > extended info if necessary. > I suggest isXXX flags instead: > isUpdated() > isAdded() - just came from an update > isMerged() > isInConflict() > isNew() - new locally > etc. -- 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] Updated: (SCM-19) resolve file status ambiguities
[ http://jira.codehaus.org/browse/SCM-19?page=all ] Emmanuel Venisse updated SCM-19: Fix Version: (was: 1.0-beta-1) 1.0-beta-2 > resolve file status ambiguities > --- > > Key: SCM-19 > URL: http://jira.codehaus.org/browse/SCM-19 > Project: Maven SCM > Type: Task > Components: maven-scm-api > Reporter: Brett Porter > Fix For: 1.0-beta-2 > > > currently ScmFileStatus just reports whatever the provider gave back, but > means different things in different SCM's. > eg. "updated" in CVS is UPDATED or PATCHED, in SVN it is UPDATED or MERGED. > "added" in CVS is UPDATED, in SVN it is ADDED. > The API should hide this from the user, though perhaps be able to give the > extended info if necessary. > I suggest isXXX flags instead: > isUpdated() > isAdded() - just came from an update > isMerged() > isInConflict() > isNew() - new locally > etc. -- 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