[jira] Updated: (SCM-161) Std.Err handling
[ http://jira.codehaus.org/browse/SCM-161?page=all ] Torbjørn EIkli Smørgrav updated SCM-161: Attachment: SCM-161_2-maven-scm-test.patch SCM-161_2-maven-scm-bazaar.patch > Std.Err handling > > > Key: SCM-161 > URL: http://jira.codehaus.org/browse/SCM-161 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-bazaar > Versions: 1.0 > Reporter: Torbjørn EIkli Smørgrav > Assignee: Torbjørn EIkli Smørgrav > Priority: Minor > Fix For: 1.0 > Attachments: SCM-161-maven-scm-api.patch, SCM-161-maven-scm-bazaar.patch, > SCM-161-maven-scm-test.patch, SCM-161_2-maven-scm-bazaar.patch, > SCM-161_2-maven-scm-test.patch > > > Std.Err is not handled very well in the Bazaar Provider -- 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-162) Add tests for remove repositories
Add tests for remove repositories - Key: SCM-162 URL: http://jira.codehaus.org/browse/SCM-162 Project: Maven SCM Type: Test Components: maven-scm-provider-bazaar Versions: 1.0-beta-3 Reporter: Torbjørn EIkli Smørgrav Only local and readonly http repositories are currently tested. We need to test that the provider can handlerepositories over eg. sftp aswell -- 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-161) Std.Err handling
Std.Err handling Key: SCM-161 URL: http://jira.codehaus.org/browse/SCM-161 Project: Maven SCM Type: Bug Components: maven-scm-provider-bazaar Versions: 1.0-beta-3 Reporter: Torbjørn EIkli Smørgrav Priority: Minor Std.Err is not handled very well in the Bazaar Provider -- 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-160) Refactored tck tests, added changelog tck test and added changelog, diff test for the bazaar provider
[ http://jira.codehaus.org/browse/SCM-160?page=all ] Torbjørn EIkli Smørgrav updated SCM-160: Attachment: MNG-160-maven-scm-provider-bazaar.patch MNG-160-maven-scm-test.patch > Refactored tck tests, added changelog tck test and added changelog, diff test > for the bazaar provider > - > > Key: SCM-160 > URL: http://jira.codehaus.org/browse/SCM-160 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-bazaar > Versions: 1.0-beta-3 > Environment: Tested on WinXp and Linux for cvs, svn and bazaar > Reporter: Torbjørn EIkli Smørgrav > Attachments: MNG-160-maven-scm-provider-bazaar.patch, > MNG-160-maven-scm-test.patch > > > Short summary: Refactored code into a new baseclass: ScmTckTestCase. Added > tests to Bazaar. > Working with my bazaar tests I found out that the tck test module had some > redundant code. > So I took the liberty to refactor the tck package a bit before I added the > final tests to the bazaar provider. > I tested the refactored test module with cvs, svn and bazaar on WinXp and > Linux. > (Bazaar had trouble with linux and bazaar 0.6, but that turned out to be a > Bazaar bug that was fixed in post 0.6 versions of Bazaar) > The refactoring consist mainly of centralizing duplicated blocks of code into > a new test base class: ScmTckTestCase. And > using a common setUp() method for all tck tests. > If you find this class ok - then you will most likly find the rest ok. -- 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-160) Refactored tck tests, added changelog tck test and added changelog, diff test for the bazaar provider
Refactored tck tests, added changelog tck test and added changelog, diff test for the bazaar provider - Key: SCM-160 URL: http://jira.codehaus.org/browse/SCM-160 Project: Maven SCM Type: Improvement Components: maven-scm-provider-bazaar Versions: 1.0-beta-3 Environment: Tested on WinXp and Linux for cvs, svn and bazaar Reporter: Torbjørn EIkli Smørgrav Short summary: Refactored code into a new baseclass: ScmTckTestCase. Added tests to Bazaar. Working with my bazaar tests I found out that the tck test module had some redundant code. So I took the liberty to refactor the tck package a bit before I added the final tests to the bazaar provider. I tested the refactored test module with cvs, svn and bazaar on WinXp and Linux. (Bazaar had trouble with linux and bazaar 0.6, but that turned out to be a Bazaar bug that was fixed in post 0.6 versions of Bazaar) The refactoring consist mainly of centralizing duplicated blocks of code into a new test base class: ScmTckTestCase. And using a common setUp() method for all tck tests. If you find this class ok - then you will most likly find the rest ok. -- 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_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] Commented: (SCM-19) resolve file status ambiguities
[ 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
[ 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-147) Add Bazaar provider documentation
[ http://jira.codehaus.org/browse/SCM-147?page=all ] Torbjørn EIkli Smørgrav updated SCM-147: Attachment: MNG-147-maven-scm-site.patch > Add Bazaar provider documentation > - > > Key: SCM-147 > URL: http://jira.codehaus.org/browse/SCM-147 > Project: Maven SCM > Type: New Feature > Components: maven-scm-site > Reporter: Torbjørn EIkli Smørgrav > Priority: Minor > Attachments: MNG-147-maven-scm-site.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
[jira] Created: (SCM-147) Add Bazaar provider documentation
Add Bazaar provider documentation - Key: SCM-147 URL: http://jira.codehaus.org/browse/SCM-147 Project: Maven SCM Type: New Feature Components: maven-scm-site Reporter: Torbjørn EIkli Smørgrav Priority: Minor -- 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-143) New SCM Provider: Bazaar
[ http://jira.codehaus.org/browse/SCM-143?page=all ] Torbjørn EIkli Smørgrav updated SCM-143: Attachment: MNG-143-maven-core.patch > New SCM Provider: Bazaar > > > Key: SCM-143 > URL: http://jira.codehaus.org/browse/SCM-143 > Project: Maven SCM > Type: New Feature > Environment: Tested by junit tests on windows and by continuum on linux. > Reporter: Torbjørn EIkli Smørgrav > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0-beta-3 > Attachments: MNG-143-maven-core.patch, MNG-Bazaar-maven-scm.patch > > > Bazaar is a distributed system developed at http://bazaar.canonical.com/ > The implementation has a few issues: > - The diff unit test has been removed due to a subtile issue in the unified > diff output. > - I have not tested too much with different repository urls eg sftp. -- 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] Reopened: (SCM-143) New SCM Provider: Bazaar
[ http://jira.codehaus.org/browse/SCM-143?page=all ] Torbjørn EIkli Smørgrav reopened SCM-143: - Complete initial patch so that all junit tests run. I cannot reproduce the junit error, but from the output given by Emmanuel Venisse I saw that the initial repository where empty. I'll add a patch that makes that initial step more robust by forcing non-recursive add and by always use absolute paths. > New SCM Provider: Bazaar > > > Key: SCM-143 > URL: http://jira.codehaus.org/browse/SCM-143 > Project: Maven SCM > Type: New Feature > Environment: Tested by junit tests on windows and by continuum on linux. > Reporter: Torbjørn EIkli Smørgrav > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0-beta-3 > Attachments: MNG-Bazaar-maven-scm.patch > > > Bazaar is a distributed system developed at http://bazaar.canonical.com/ > The implementation has a few issues: > - The diff unit test has been removed due to a subtile issue in the unified > diff output. > - I have not tested too much with different repository urls eg sftp. -- 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-143) New SCM Provider: Bazaar
New SCM Provider: Bazaar Key: SCM-143 URL: http://jira.codehaus.org/browse/SCM-143 Project: Maven SCM Type: New Feature Environment: Tested by junit tests on windows and by continuum on linux. Reporter: Torbjørn EIkli Smørgrav Priority: Minor Attachments: MNG-Bazaar-maven-scm.patch Bazaar is a distributed system developed at http://bazaar.canonical.com/ The implementation has a few issues: - The diff unit test has been removed due to a subtile issue in the unified diff output. - I have not tested too much with different repository urls eg sftp. -- 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
