Re: [vote] Release Maven-SCM 1.0 final
+1ArnaudOn 2/24/06, dan tran <[EMAIL PROTECTED]> wrote: +1, plus upload the latest maven-scm beta3 snapshot, I can run it against my nightly release build. -Dan On 2/24/06, Lukas Theussl <[EMAIL PROTECTED] > wrote: +1LukasEmmanuel Venisse wrote:> Hi everyone,>> I'd like to release 1.0 final of Maven-SCM. All APIs are stable since a> long time and we didn't find any blocker issues since 1.0-beta-2 release.>> The list of issues fixed are :> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10527&fixfor=12346>>> We have now 3 issues that i will fix before the release.>> I'll leave the vote open for the customary 72 hours before summarizing. > Please cast your vote as:>> [ ] +1 Yes, release> [ ] 0 No opinion> [ ] -1 No, don't release>> Here's my +1.>> Cheers,>> Emmanuel>
RE: [vote] Release Maven-SCM 1.0 final
-0 I got several Perforce patches in the last 2-3 days that I would like to get in before the release. Do you mind if I sneak them in tomorrow? You are welcome to apply them if you have the time today (SCM-16x) but I'm slammed at work right now. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Friday, February 24, 2006 11:56 AM To: scm-dev@maven.apache.org Subject: [vote] Release Maven-SCM 1.0 final Hi everyone, I'd like to release 1.0 final of Maven-SCM. All APIs are stable since a long time and we didn't find any blocker issues since 1.0-beta-2 release. The list of issues fixed are : http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10527 &fixfor=12346 We have now 3 issues that i will fix before the release. I'll leave the vote open for the customary 72 hours before summarizing. Please cast your vote as: [ ] +1 Yes, release [ ] 0 No opinion [ ] -1 No, don't release Here's my +1. Cheers, Emmanuel
[jira] Deleted: (SCM-10) Use cvslib instead of cvs command line in cvs provider
[ http://jira.codehaus.org/browse/SCM-10?page=all ] Emmanuel Venisse deleted SCM-10: > Use cvslib instead of cvs command line in cvs provider > -- > > Key: SCM-10 > URL: http://jira.codehaus.org/browse/SCM-10 > Project: Maven SCM > Type: Task > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > > > if cvslib support ext protocol. -- 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-161) Std.Err handling
[ http://jira.codehaus.org/browse/SCM-161?page=all ] Emmanuel Venisse updated SCM-161: - Fix Version: 1.0 > 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 > > > 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] Commented: (SCM-161) Std.Err handling
[ http://jira.codehaus.org/browse/SCM-161?page=comments#action_59416 ] Emmanuel Venisse commented on SCM-161: -- I applied maven-scm-api.patch. Can you regenerate other patches with new code in scm? > 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 > Attachments: SCM-161-maven-scm-api.patch, SCM-161-maven-scm-bazaar.patch, > SCM-161-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] Closed: (SCM-19) resolve file status ambiguities
[ 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] Closed: (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 ] Emmanuel Venisse closed SCM-160: Resolution: Fixed Fix Version: 1.0 > 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 > Environment: Tested on WinXp and Linux for cvs, svn and bazaar > Reporter: Torbjørn EIkli Smørgrav > Assignee: Torbjørn EIkli Smørgrav > Fix For: 1.0 > Attachments: MNG-160-maven-scm-provider-bazaar.patch, > MNG-160-maven-scm-test.patch, MNG-160_2-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] Closed: (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 ] Emmanuel Venisse closed SCM-160: Resolution: Fixed Applied. Thanks. > 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 > Environment: Tested on WinXp and Linux for cvs, svn and bazaar > Reporter: Torbjørn EIkli Smørgrav > Assignee: Torbjørn EIkli Smørgrav > Attachments: MNG-160-maven-scm-provider-bazaar.patch, > MNG-160-maven-scm-test.patch, MNG-160_2-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] Reopened: (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 ] Emmanuel Venisse reopened SCM-160: -- > 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 > Environment: Tested on WinXp and Linux for cvs, svn and bazaar > Reporter: Torbjørn EIkli Smørgrav > Assignee: Torbjørn EIkli Smørgrav > Attachments: MNG-160-maven-scm-provider-bazaar.patch, > MNG-160-maven-scm-test.patch, MNG-160_2-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] Updated: (SCM-121) Intermittent CVS test failures
[ http://jira.codehaus.org/browse/SCM-121?page=all ] Emmanuel Venisse updated SCM-121: - Fix Version: (was: 1.0) > Intermittent CVS test failures > -- > > Key: SCM-121 > URL: http://jira.codehaus.org/browse/SCM-121 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0 > Reporter: Mike Perham > Attachments: cvs.exe > > > Dan and I continue to have test failures when trying to compile the cvs > plugin in our environment. I emailed these problems to the scm-dev list > about a week ago. -- 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-31) The scm url validator should return a code corresponding to the error
[ http://jira.codehaus.org/browse/SCM-31?page=all ] Emmanuel Venisse updated SCM-31: Fix Version: (was: 1.0) 1.0.1 > The scm url validator should return a code corresponding to the error > - > > Key: SCM-31 > URL: http://jira.codehaus.org/browse/SCM-31 > Project: Maven SCM > Type: Improvement > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0.1 > > > I would like an error code to be returned so that I can use the error code to > select an i18n key that will provide users with a localized error message. -- 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-2) Create POJO facade
[ http://jira.codehaus.org/browse/SCM-2?page=all ] Emmanuel Venisse updated SCM-2: --- Fix Version: (was: 1.0) 1.0.1 > Create POJO facade > -- > > Key: SCM-2 > URL: http://jira.codehaus.org/browse/SCM-2 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Fix For: 1.0.1 > > > Make an easy to use POJO facade for maven-scm. -- 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-18) complete commands and expose through ScmManager
[ http://jira.codehaus.org/browse/SCM-18?page=all ] Emmanuel Venisse updated SCM-18: Fix Version: (was: 1.0) 1.0.1 > complete commands and expose through ScmManager > --- > > Key: SCM-18 > URL: http://jira.codehaus.org/browse/SCM-18 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-clearcase, maven-scm-provider-starteam, > maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-svn, > maven-scm-provider-perforce, maven-scm-api > Reporter: Brett Porter > Fix For: 1.0.1 > > > many commands are not completely implemented, or not implemented at all, and > some that are have not been exposed through the ScmManager interface. > These all need to be rounded out and tested via the TCK for a final 1.0 > release. -- 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-5) Create user guide/Guide for the impatient programmer (gipper)
[ http://jira.codehaus.org/browse/SCM-5?page=all ] Emmanuel Venisse updated SCM-5: --- Fix Version: (was: 1.0) Component: documentation > Create user guide/Guide for the impatient programmer (gipper) > - > > Key: SCM-5 > URL: http://jira.codehaus.org/browse/SCM-5 > Project: Maven SCM > Type: Task > Components: documentation > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > > -- 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-17) test structure needs further clean up
[ http://jira.codehaus.org/browse/SCM-17?page=all ] Emmanuel Venisse updated SCM-17: Fix Version: (was: 1.0) 1.0.1 > test structure needs further clean up > - > > Key: SCM-17 > URL: http://jira.codehaus.org/browse/SCM-17 > Project: Maven SCM > Type: Test > Components: maven-scm-provider-clearcase, maven-scm-provider-starteam, > maven-scm-provider-local, maven-scm-provider-cvs, > maven-scm-provider-perforce, maven-scm-provider-svn > Reporter: Brett Porter > Fix For: 1.0.1 > > > The following is needed: > - all providers need to utilise the TCK where possible. > - any tests in providers that can be generalised should be moved to the TCK > - other tests in the providers should just test provider specific functions, > and probably not be integration tests like the TCK is > - need further tests for other commands, including those yet to be added > - review coverage for each 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-154) Bazaar tests should not assume bzr is installed
[ http://jira.codehaus.org/browse/SCM-154?page=all ] Emmanuel Venisse updated SCM-154: - Fix Version: (was: 1.0) 1.0.1 > Bazaar tests should not assume bzr is installed > --- > > Key: SCM-154 > URL: http://jira.codehaus.org/browse/SCM-154 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-bazaar > Versions: 1.0 > Reporter: Mike Perham > Assignee: Torbjørn EIkli Smørgrav > Priority: Critical > Fix For: 1.0.1 > > > Bazaar breaks my SCM build because it assumes it is installed. I do not > think the user should be forced to install Bazaar just to compile the SCM > codebase. See the StarTeam, Perforce and ClearCase providers for examples of > providers which do not assume an installation. -- 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-6) Development/Testing guide
[ http://jira.codehaus.org/browse/SCM-6?page=all ] Emmanuel Venisse updated SCM-6: --- Fix Version: (was: 1.0) Component: documentation > Development/Testing guide > - > > Key: SCM-6 > URL: http://jira.codehaus.org/browse/SCM-6 > Project: Maven SCM > Type: Task > Components: documentation > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > > > Guide on how to create new scm providers utilizing the abstract scm test case > for easy testing. -- 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-139) Create a utility class for scm url checking/parsing
[ http://jira.codehaus.org/browse/SCM-139?page=comments#action_59384 ] Emmanuel Venisse commented on SCM-139: -- i thought to a patch that remove "lot of code in different place" and use your class instead. > Create a utility class for scm url checking/parsing > --- > > Key: SCM-139 > URL: http://jira.codehaus.org/browse/SCM-139 > Project: Maven SCM > Type: New Feature > Components: maven-scm-api > Reporter: Dennis Lundberg > Attachments: SCM-139-2.zip, SCM-139.zip, ScmUrlUtils.java > > > There is a lot of code in different places, both in maven-scm and elsewhere, > that checks and parses scm url:s. I propose that a utility class ScmUrlUtils > be crated in maven-scm-api where such code (static methods) can be placed. > The code there should not be scm provider specific. This should be > accompanied by a test suite. > This concept might also be applied to individual scm providers, e.g. there > could be a CvsScmUrlUtils in maven-scm-provider-cvs. -- 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
