You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by ji...@codehaus.org on 2005/01/01 07:39:56 UTC
[jira] Created: (SCM-19) resolve file status ambiguities
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/SCM-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: SCM-19
Summary: resolve file status ambiguities
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Maven SCM
Components:
maven-scm-api
Fix Fors:
1.0
Assignee:
Reporter: Brett Porter
Created: Sat, 1 Jan 2005 1:39 AM
Updated: Sat, 1 Jan 2005 1:39 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (SCM-19) resolve file status ambiguities
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-19?page=all ]
Emmanuel Venisse updated SCM-19:
--------------------------------
Fix Version: (was: 1.0-beta-3)
1.0
> 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
>
>
> 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
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-19?page=all ]
Emmanuel Venisse updated SCM-19:
--------------------------------
Fix Version: (was: 1.0-beta-2)
1.0-beta-3
> 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-3
>
>
> 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] Commented: (SCM-19) resolve file status ambiguities
Posted by "Torbj?rn EIkli Sm?rgrav (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-19?page=comments#action_58422 ]
Torbjørn EIkli Smørgrav commented on SCM-19:
--------------------------------------------
I realized that I was not very consistent between my patch and my comment above.
To clearify:
Some of the status are related to the status of the file in the working tree versus the repository eg. added and removed.
Others are just a tag that the file is involved in a transaction with the repository eg. checkedin and checkout.
Some status eg. update, added and removed are used in both cases and I think it should be separated.
Updated should In my opinion be a transaction tag.
T
> 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
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (SCM-19) resolve file status ambiguities
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-19?page=all ]
Emmanuel Venisse closed SCM-19:
-------------------------------
Assign To: Torbjørn EIkli Smørgrav
Resolution: Fixed
Applied. Thanks.
> 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
> Assignee: Torbjørn EIkli Smørgrav
> 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
Posted by "Torbj?rn EIkli Sm?rgrav (JIRA)" <ji...@codehaus.org>.
[ 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
Posted by "Torbj?rn EIkli Sm?rgrav (JIRA)" <ji...@codehaus.org>.
[ 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