[
https://issues.apache.org/jira/browse/SCM-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964277#comment-17964277
]
Olivier Lamy commented on SCM-19:
---------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#281|https://github.com/apache/maven-scm/issues/281].
> resolve file status ambiguities
> -------------------------------
>
> Key: SCM-19
> URL: https://issues.apache.org/jira/browse/SCM-19
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Task
> Components: maven-scm-api
> Reporter: Brett Porter
> Assignee: Torbjorn Eikli Smorgrav
> Priority: Major
> Fix For: 1.0-beta-3
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
