Re: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider
That's probaly it, thanks. - Brett Torbjørn Smørgrav wrote: > Have you tested Bazaar manually? > > Form the test log it clear that every command fails > due to an import error in Bazaar. > > Check if the cElementTree module is installed properly by running: > $ python -c "import cElementTree" > > Torbjørn > > > > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 24. mars 2006 08:03 > To: scm-dev@maven.apache.org > Subject: Re: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider > > > Any ideas on this? bzr 0.7 seems to be properly installed now. Can the > output of the tests be improved? > > - Brett > > Continuum Build Server wrote: >> Online report : > http://ci.codehaus.org/continuum-maven/servlet/continuum/target/ProjectBuild > .vm/view/ProjectBuild/id/66/buildId/714 >> Build statistics: >> State: Failed >> Previous State: Failed >> Started at: Thu, 23 Mar 2006 22:50:10 -0800 >> Finished at: Thu, 23 Mar 2006 22:50:20 -0800 >> Total time: 10s >> Build Trigger: Forced >> Exit code: 1 >> Building machine hostname: cheddar.simulalabs.com >> Operating system : Linux(unknown) >> Java version : 1.5.0_03(Sun Microsystems Inc.) >> >> Changes >> No files changed >> >> > >> Output: >> > **** >> [INFO] Scanning for projects... >> > [INFO] - > --- >> [INFO] Building Maven SCM Bazaar Provider >> [INFO]task-segment: [clean, install] >> > [INFO] - > --- >> [INFO] [clean:clean] >> [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target >> [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target/classes >> [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target/test-classes >> [INFO] [resources:resources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:compile] >> Compiling 19 source files to > /home/nobody/continuum-maven/working-directory/66/target/classes >> [INFO] [resources:testResources] >> [INFO] Using default encoding to copy filtered resources. >> [INFO] [compiler:testCompile] >> Compiling 7 source files to > /home/nobody/continuum-maven/working-directory/66/target/test-classes >> [INFO] [surefire:test] >> [INFO] Setting reports dir: > /home/nobody/continuum-maven/working-directory/66/target/surefire-reports >> --- >> T E S T S >> --- >> [surefire] Running > org.apache.maven.scm.provider.bazaar.command.checkin.BazaarCheckInCommandTes > t >> EXECUTING: bzr init >> failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' >> [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown >> Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch >> failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' >> [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeEXECUTING: bzr add > /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml > /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme. > txt > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/mai > n/java/Application.java > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/tes > t/java/Test.java >> failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' >> [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown >> Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch >> failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' >> [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeEXECUTING: bzr init >> failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' >> [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown >> Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch >> failed to open t
RE: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider
I'll change the test output to be more spesific about where the error occured, if its the bazaar installation or if its due to unexpected response from bazaar. Torbjørn -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 24. mars 2006 08:03 To: scm-dev@maven.apache.org Subject: Re: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider Any ideas on this? bzr 0.7 seems to be properly installed now. Can the output of the tests be improved? - Brett Continuum Build Server wrote: > Online report : http://ci.codehaus.org/continuum-maven/servlet/continuum/target/ProjectBuild .vm/view/ProjectBuild/id/66/buildId/714 > Build statistics: > State: Failed > Previous State: Failed > Started at: Thu, 23 Mar 2006 22:50:10 -0800 > Finished at: Thu, 23 Mar 2006 22:50:20 -0800 > Total time: 10s > Build Trigger: Forced > Exit code: 1 > Building machine hostname: cheddar.simulalabs.com > Operating system : Linux(unknown) > Java version : 1.5.0_03(Sun Microsystems Inc.) > > Changes > No files changed > > > Output: > > [INFO] Scanning for projects... > [INFO] ----- --- > [INFO] Building Maven SCM Bazaar Provider > [INFO]task-segment: [clean, install] > [INFO] - --- > [INFO] [clean:clean] > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 19 source files to /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 7 source files to /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: /home/nobody/continuum-maven/working-directory/66/target/surefire-reports > > --- > T E S T S > --- > [surefire] Running org.apache.maven.scm.provider.bazaar.command.checkin.BazaarCheckInCommandTes t > EXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr add /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme. txt /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/mai n/java/Application.java /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/tes t/java/Test.java > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr add /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme. txt /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/mai n/java/Application.java /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/tes t/java/Test.java > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module n
RE: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider
Have you tested Bazaar manually? Form the test log it clear that every command fails due to an import error in Bazaar. Check if the cElementTree module is installed properly by running: $ python -c "import cElementTree" Torbjørn -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 24. mars 2006 08:03 To: scm-dev@maven.apache.org Subject: Re: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider Any ideas on this? bzr 0.7 seems to be properly installed now. Can the output of the tests be improved? - Brett Continuum Build Server wrote: > Online report : http://ci.codehaus.org/continuum-maven/servlet/continuum/target/ProjectBuild .vm/view/ProjectBuild/id/66/buildId/714 > Build statistics: > State: Failed > Previous State: Failed > Started at: Thu, 23 Mar 2006 22:50:10 -0800 > Finished at: Thu, 23 Mar 2006 22:50:20 -0800 > Total time: 10s > Build Trigger: Forced > Exit code: 1 > Building machine hostname: cheddar.simulalabs.com > Operating system : Linux(unknown) > Java version : 1.5.0_03(Sun Microsystems Inc.) > > Changes > No files changed > > > Output: > > [INFO] Scanning for projects... > [INFO] ----- --- > [INFO] Building Maven SCM Bazaar Provider > [INFO]task-segment: [clean, install] > [INFO] - --- > [INFO] [clean:clean] > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] Deleting directory /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 19 source files to /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 7 source files to /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: /home/nobody/continuum-maven/working-directory/66/target/surefire-reports > > --- > T E S T S > --- > [surefire] Running org.apache.maven.scm.provider.bazaar.command.checkin.BazaarCheckInCommandTes t > EXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr add /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme. txt /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/mai n/java/Application.java /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/tes t/java/Test.java > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeBazaar version: Unknown > Working directory: /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named elementtree.ElementTreeEXECUTING: bzr add /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme. txt /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/mai n/java/Application.java /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/tes t/java/Test.java > failed to open trace file: [Errno 13] Permission denied: &
Re: [continuum] BUILD FAILURE: Maven SCM Bazaar Provider
Any ideas on this? bzr 0.7 seems to be properly installed now. Can the output of the tests be improved? - Brett Continuum Build Server wrote: > Online report : > http://ci.codehaus.org/continuum-maven/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/66/buildId/714 > Build statistics: > State: Failed > Previous State: Failed > Started at: Thu, 23 Mar 2006 22:50:10 -0800 > Finished at: Thu, 23 Mar 2006 22:50:20 -0800 > Total time: 10s > Build Trigger: Forced > Exit code: 1 > Building machine hostname: cheddar.simulalabs.com > Operating system : Linux(unknown) > Java version : 1.5.0_03(Sun Microsystems Inc.) > > Changes > No files changed > > > Output: > > [INFO] Scanning for projects... > [INFO] > ---- > [INFO] Building Maven SCM Bazaar Provider > [INFO]task-segment: [clean, install] > [INFO] > > [INFO] [clean:clean] > [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target > [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] Deleting directory > /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 19 source files to > /home/nobody/continuum-maven/working-directory/66/target/classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 7 source files to > /home/nobody/continuum-maven/working-directory/66/target/test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: > /home/nobody/continuum-maven/working-directory/66/target/surefire-reports > > --- > T E S T S > --- > [surefire] Running > org.apache.maven.scm.provider.bazaar.command.checkin.BazaarCheckInCommandTest > EXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown > Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeEXECUTING: bzr add > /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml > /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme.txt > > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/main/java/Application.java > > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/test/java/Test.java > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown > Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeEXECUTING: bzr init > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown > Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeEXECUTING: bzr add > /home/nobody/continuum-maven/working-directory/66/target/test-branch/pom.xml > /home/nobody/continuum-maven/working-directory/66/target/test-branch/readme.txt > > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/main/java/Application.java > > /home/nobody/continuum-maven/working-directory/66/target/test-branch/src/test/java/Test.java > failed to open trace file: [Errno 13] Permission denied: '/.bzr.log' > [ERROR] exceptions.ImportError: No module named > elementtree.ElementTreeBazaar version: Unknown > Working directory: > /home/nobody/continuum-maven/working-directory/66/target/test-branch > failed to open trace file: [
[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] Commented: (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=comments#action_58542 ] Emmanuel Venisse commented on SCM-160: -- ScmTckTestCase is missing > 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] 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
Re: Bazaar Provider
1.0-beta-3 will be release before end of Febrary. So if you do them for next week, it's great. Emmanuel Torbjørn Smørgrav a écrit : When is 1.0-beta-3 scheduled to? I'll try to do some of it this weekend, and then I can do the rest at the end of next week. T -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 16:33 To: scm-dev@maven.apache.org Subject: Re: Bazaar Provider Open an issue with this file and you'll add a changelog parser test when it will be ready. You can file issues for other point and assigned them to you. When do you think you'll can do them? I'd like commit fixes before 1.0-beta-3 Emmanuel Torbjørn Smørgrav a écrit : Do you want the output just as below or documented somewhere else? Sample changelog output from Bazaar: revno: 3 committer: [EMAIL PROTECTED] timestamp: Thu 2006-01-26 16:55:47 +0100 message: Inventory stuff revno: 2 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:42:54 +0100 message: Remove comment revno: 1 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:40:14 +0100 message: Initial revision FYI: I have a couple of other issues in the pipeline: 1. Diff cmd is not passing the unit test due to the @@ tag and wrong ScmFileStatus 2. Checkin unit test is failing on linux with bazaar 0.6 3. Add changelog test 4. Test urls with ftps and ftp 5. Proper std.err processing Regards Torbjørn -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 15:11 To: scm-dev@maven.apache.org Subject: Bazaar Provider Hi Torbjorn, Can you provide a sample output of bazaar changelog output and add a changelog consumer test? Thanks Emmanuel
RE: Bazaar Provider
When is 1.0-beta-3 scheduled to? I'll try to do some of it this weekend, and then I can do the rest at the end of next week. T -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 16:33 To: scm-dev@maven.apache.org Subject: Re: Bazaar Provider Open an issue with this file and you'll add a changelog parser test when it will be ready. You can file issues for other point and assigned them to you. When do you think you'll can do them? I'd like commit fixes before 1.0-beta-3 Emmanuel Torbjørn Smørgrav a écrit : > Do you want the output just as below or documented somewhere else? > > Sample changelog output from Bazaar: > > > revno: 3 > committer: [EMAIL PROTECTED] > timestamp: Thu 2006-01-26 16:55:47 +0100 > message: > Inventory stuff > > revno: 2 > committer: [EMAIL PROTECTED] > timestamp: Tue 2006-01-03 15:42:54 +0100 > message: > Remove comment > > revno: 1 > committer: [EMAIL PROTECTED] > timestamp: Tue 2006-01-03 15:40:14 +0100 > message: > Initial revision > > FYI: I have a couple of other issues in the pipeline: > 1. Diff cmd is not passing the unit test due to the @@ tag and wrong > ScmFileStatus > 2. Checkin unit test is failing on linux with bazaar 0.6 > 3. Add changelog test > 4. Test urls with ftps and ftp > 5. Proper std.err processing > > Regards > Torbjørn > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: 2. februar 2006 15:11 > To: scm-dev@maven.apache.org > Subject: Bazaar Provider > > > Hi Torbjorn, > > Can you provide a sample output of bazaar changelog output and add a > changelog consumer test? > > Thanks > Emmanuel > > > >
RE: Bazaar Provider
Do you want the output just as below or documented somewhere else? Sample changelog output from Bazaar: revno: 3 committer: [EMAIL PROTECTED] timestamp: Thu 2006-01-26 16:55:47 +0100 message: Inventory stuff revno: 2 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:42:54 +0100 message: Remove comment revno: 1 committer: [EMAIL PROTECTED] timestamp: Tue 2006-01-03 15:40:14 +0100 message: Initial revision FYI: I have a couple of other issues in the pipeline: 1. Diff cmd is not passing the unit test due to the @@ tag and wrong ScmFileStatus 2. Checkin unit test is failing on linux with bazaar 0.6 3. Add changelog test 4. Test urls with ftps and ftp 5. Proper std.err processing Regards Torbjørn -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 2. februar 2006 15:11 To: scm-dev@maven.apache.org Subject: Bazaar Provider Hi Torbjorn, Can you provide a sample output of bazaar changelog output and add a changelog consumer test? Thanks Emmanuel
[jira] Closed: (SCM-147) Add Bazaar provider documentation
[ http://jira.codehaus.org/browse/SCM-147?page=all ] Emmanuel Venisse closed SCM-147: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. Thanks. > 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 > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0-beta-3 > 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] 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
Re: Bazaar provider - howto submit
Torbjørn Smørgrav wrote: Hi, I've finally finished the Bazaar provider. What is the procedure to get it into the maven-scm tree? Regards Torbjørn Hello, The first thing to do is create a new issue for this in jira: http://jira.codehaus.org/browse/SCM Read through this document: http://maven.apache.org/guides/development/guide-m2-development.html in particular the sections "Creating and submitting a patch" and "Maven Code Style". Then attach your patch to the jira issue you created earlier. -- Dennis Lundberg
Re: Bazaar provider - howto submit
File an issue in jira (http://jira.codehaus.org/browse/SCM) and attach your code. Emmanuel Torbjørn Smørgrav a écrit : Hi, I've finally finished the Bazaar provider. What is the procedure to get it into the maven-scm tree? Regards Torbjørn
Bazaar provider - howto submit
Hi, I've finally finished the Bazaar provider. What is the procedure to get it into the maven-scm tree? Regards Torbjørn
