[jira] Closed: (SCM-161) Std.Err handling
[ http://jira.codehaus.org/browse/SCM-161?page=all ] Emmanuel Venisse closed SCM-161: Resolution: Fixed Applied. Thanks. > 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] Closed: (SCM-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=all ] Emmanuel Venisse closed SCM-13: --- Assign To: Emmanuel Venisse Resolution: Fixed All patches are applied with some modifications like links to maven-settings that are removed. Thanks David This provider will be release when a new version of javasvn (1.0.4) will be release. This version will support file protocol so we'll can test it correctly with TCK. > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0 > Attachments: SCM-13-maven-scm-api.patch, > SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch, > SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz, > tmate.org.javasvn.tar.gz > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- 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-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59501 ] Emmanuel Venisse commented on SCM-165: -- update and changelog commands doesn't run necessarily as part of a single VM invocation. > PerforceChangeLogCommand needs to use the same clientspec as the update > command > --- > > Key: SCM-165 > URL: http://jira.codehaus.org/browse/SCM-165 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0 > Reporter: John Didion > Assignee: Mike Perham > Priority: Critical > Attachments: PerforceChangeLogCommand.diff, svn.diff > > > The PerforceChangeLogCommand as written does not work if the update was done > with the client spec generated by the checkout/update command. The attached > diff will fix the problem. -- 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-165) PerforceChangeLogCommand needs to use the same clientspec as the update command
[ http://jira.codehaus.org/browse/SCM-165?page=comments#action_59500 ] Emmanuel Venisse commented on SCM-165: -- changelog command must work in standalone mode (require by changelog mojo and by changelog report mojo) AND as part of update command (require by update mojo and continuum). > PerforceChangeLogCommand needs to use the same clientspec as the update > command > --- > > Key: SCM-165 > URL: http://jira.codehaus.org/browse/SCM-165 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0 > Reporter: John Didion > Assignee: Mike Perham > Priority: Critical > Attachments: PerforceChangeLogCommand.diff, svn.diff > > > The PerforceChangeLogCommand as written does not work if the update was done > with the client spec generated by the checkout/update command. The attached > diff will fix the problem. -- 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_59466 ] Emmanuel Venisse commented on SCM-139: -- yes > 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
[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
[jira] Commented: (SCM-139) Create a utility class for scm url checking/parsing
[ http://jira.codehaus.org/browse/SCM-139?page=comments#action_59259 ] Emmanuel Venisse commented on SCM-139: -- It will be good if you can provide a patch that remove all duplicated code > 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
[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] Commented: (SCM-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=comments#action_58348 ] Emmanuel Venisse commented on SCM-13: - >From TMate support: Forgot one more thing to mention - JavaSVN only supports repositories of type 'fsfs'. This is a default type of repository, and probably most widely used, but there are aslo 'bdb' (berkley db based) repositories that are not supported, and so far there are no plans to support them. > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > Fix For: 1.0 > Attachments: SCM-13-maven-scm-api.patch, > SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch, > SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz, > tmate.org.javasvn.tar.gz > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- 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-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=comments#action_58347 ] Emmanuel Venisse commented on SCM-13: - >From TMate support : Hello Emmanuel, "file" protocol is already supported in development version in "trunk" and will be included into version 1.1.0 that is currently planned to be published in March 2006. You may already use "file" protocol if you will checkout and build JavaSVN from "http://svn.tmate.org/repos/jsvn/trunk/";. To enable "file" protocol, you should first make the following call: FSRepositoryFactory.setup(); // similar approach is used for DAV and svn protocols support. "file" protocol support pass mostly all python tests, but right now I would not recommend you to use it against production repositories, and also it is not yet optimized, so works somewhat slow. > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > Fix For: 1.0 > Attachments: SCM-13-maven-scm-api.patch, > SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch, > SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz, > tmate.org.javasvn.tar.gz > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- 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-29) test with CVS NT
[ http://jira.codehaus.org/browse/SCM-29?page=comments#action_58139 ] Emmanuel Venisse commented on SCM-29: - I don't agree. I prefer remove my check for CVSNT and let cvs send the error message if it doesn't support a tag format. We'll have the same result (a ScmException) if it doesn't supported. > test with CVS NT > > > Key: SCM-29 > URL: http://jira.codehaus.org/browse/SCM-29 > Project: Maven SCM > Type: Test > Components: maven-scm-provider-cvs > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > Vincent reported test failures on CVS NT... test it and fix if required. -- 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-159) NumberFormatException when you include a port in your scm url
[ http://jira.codehaus.org/browse/SCM-159?page=all ] Emmanuel Venisse closed SCM-159: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. Thanks. > NumberFormatException when you include a port in your scm url > - > > Key: SCM-159 > URL: http://jira.codehaus.org/browse/SCM-159 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-svn > Versions: 1.0-beta-3 > Environment: osx 10.4.4, java 1.4.2_09 > Reporter: Julian Wood > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-159-maven-scm-provider-svn.patch > > > This bug came about in a strange way. I have always had URLs like: > scm:svn:http://[EMAIL PROTECTED]:8800/pmgt/trunk > and they have always worked for me. But when I came to write a small plugin > which used scm, I found I kept getting this error: > org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred > in the status process. >... > Caused by: org.apache.maven.plugin.MojoExecutionException: An error is > occurred in the status process. >... > Caused by: org.apache.maven.scm.ScmException: Can't load the scm provider. >... > Caused by: java.lang.NumberFormatException: For input string: ":8800" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:468) > at java.lang.Integer.parseInt(Integer.java:518) > at > org.apache.maven.scm.provider.svn.repository.SvnScmProviderRepository.parseUrl(SvnScmProviderRepository.java:126) > at > org.apache.maven.scm.provider.svn.repository.SvnScmProviderRepository.(SvnScmProviderRepository.java:42) > at > org.apache.maven.scm.provider.svn.SvnScmProvider.parseScmUrl(SvnScmProvider.java:251) > at > org.apache.maven.scm.provider.svn.SvnScmProvider.makeProviderScmRepository(SvnScmProvider.java:80) > at > org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:134) > at > org.apache.maven.plugins.release.helpers.ScmHelper.getScmRepository(ScmHelper.java:86) > Now this of course didn't happen during release:prepare, or with the > changelog plugin. So I changed around the tag, and it > turns out that it can be anything and these two goals still work, presumably > because sufficient svn information is somewhere else. > In any case, I needed it to work for my plugin, and found that the index of > the colon is off by one character in SvnScmProviderRepository.parseUrl, as > the error message implies. > This patch fixes that, and adds some unit tests. -- 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-154) Bazaar tests should not assume bzr is installed
[ http://jira.codehaus.org/browse/SCM-154?page=comments#action_58071 ] Emmanuel Venisse commented on SCM-154: -- I added a note in bazaar provider directory > 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-beta-3 > Reporter: Mike Perham > Priority: Critical > Fix For: 1.0-beta-3 > > > 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] Commented: (SCM-121) Intermittent CVS test failures
[ http://jira.codehaus.org/browse/SCM-121?page=comments#action_58072 ] Emmanuel Venisse commented on SCM-121: -- Tests works fine with your cvs.exe > 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-beta-3 > Reporter: Mike Perham > Fix For: 1.0 > 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] Commented: (SCM-154) Bazaar tests should not assume bzr is installed
[ http://jira.codehaus.org/browse/SCM-154?page=comments#action_58069 ] Emmanuel Venisse commented on SCM-154: -- I'm not really agree. We require installed cvs and svn for tests of cvs and svn providers because they are free, easy to install. With them we can run TCK tests. I consider it's the same for bazaar. Clearcase, Perforce and Starteam aren't require by tests because they aren't available for free or easy to install. > 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-beta-3 > Reporter: Mike Perham > Priority: Critical > Fix For: 1.0-beta-3 > > > 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] Closed: (SCM-29) test with CVS NT
[ http://jira.codehaus.org/browse/SCM-29?page=all ] Emmanuel Venisse closed SCM-29: --- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: (was: 1.0) 1.0-beta-3 All tests are ok with CVSNT > test with CVS NT > > > Key: SCM-29 > URL: http://jira.codehaus.org/browse/SCM-29 > Project: Maven SCM > Type: Test > Components: maven-scm-provider-cvs > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > Vincent reported test failures on CVS NT... test it and fix if required. -- 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-2) Create POJO facade
[ http://jira.codehaus.org/browse/SCM-2?page=comments#action_57981 ] Emmanuel Venisse commented on SCM-2: What do you think if we use ScmHelper from maven release plugin? > 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 > > > 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] Commented: (SCM-148) specify flags to svn
[ http://jira.codehaus.org/browse/SCM-148?page=comments#action_57976 ] Emmanuel Venisse commented on SCM-148: -- I don't have deploy updated site yet, i'll do it for 1.0-beta-3 release. The updated documentation is there : http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-site/src/site/apt/subversion.apt?rev=375374&view=markup > specify flags to svn > > > Key: SCM-148 > URL: http://jira.codehaus.org/browse/SCM-148 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: David Saff > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > I'd like an easy way to specify flags that should be passed to the svn > command when updating my project. For example, I'd like to pass the > --config-dir flag to svn, to redirect it to a different configuration > directory. -- 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-148) specify flags to svn
[ http://jira.codehaus.org/browse/SCM-148?page=comments#action_57759 ] Emmanuel Venisse commented on SCM-148: -- i asked you because it isn't the same code. > specify flags to svn > > > Key: SCM-148 > URL: http://jira.codehaus.org/browse/SCM-148 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: David Saff > Fix For: 1.0-beta-3 > > > I'd like an easy way to specify flags that should be passed to the svn > command when updating my project. For example, I'd like to pass the > --config-dir flag to svn, to redirect it to a different configuration > directory. -- 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-113) Support persistent and transient clientspecs
[ http://jira.codehaus.org/browse/SCM-113?page=comments#action_57758 ] Emmanuel Venisse commented on SCM-113: -- I don't think, so file an issue on continuum and link it to this issue. > Support persistent and transient clientspecs > > > Key: SCM-113 > URL: http://jira.codehaus.org/browse/SCM-113 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-perforce > Versions: 1.0-beta-3 > Reporter: Mike Perham > Assignee: Mike Perham > Fix For: 1.0-beta-3 > > > Continuum needs a persistent clientspec because it needs to update a > project's source code and build it once an hour. On larger projects a > complete resync might take 10-20 minutes so it is necessary to keep a > clientspec around for that Continuum project build so syncs only take a few > seconds. > However, the Maven Release plugin may need to be used by tens or even > hundreds of developers to release any number of small modules. Currently > this would mean lots of clientspecs being created for the release checkout > which are reused very infrequently. Here I would prefer to create the > clientspec, do the checkout, build and then delete the clientspec. This is > what I term a transient clientspec. > The Perforce plugin would need to default to one mode and support some sort > of hint which tells it which mode to operate in. -- 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-120) ClearCase Changelog test failure
[ http://jira.codehaus.org/browse/SCM-120?page=all ] Emmanuel Venisse closed SCM-120: > ClearCase Changelog test failure > > > Key: SCM-120 > URL: http://jira.codehaus.org/browse/SCM-120 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Versions: 1.0-beta-3 > Reporter: Mike Perham > Assignee: Mike Perham > Fix For: 1.0-beta-3 > > > junit.framework.ComparisonFailure: expected:<...10...> but was:<...09...> > at junit.framework.Assert.assertEquals(Assert.java:81) > at junit.framework.Assert.assertEquals(Assert.java:87) > at > org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommandTest.testCommandLine(ClearCaseChangeLogCommandTest.java:97) > at > org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommandTest.testGetCommandLineWithStartDate(ClearCaseChangeLogCommandTest.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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-119) Perforce provider should only append "/..." to view if necessary
[ http://jira.codehaus.org/browse/SCM-119?page=all ] Emmanuel Venisse closed SCM-119: > Perforce provider should only append "/..." to view if necessary > > > Key: SCM-119 > URL: http://jira.codehaus.org/browse/SCM-119 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Reporter: Neil Padgen > Assignee: Mike Perham > Fix For: 1.0-beta-3 > Attachments: patch > > > When creating a clientspec, maven-scm-provider-perforce currently appends > "/..." to the SCM URL regardless of what is already there. But other plugins > (such as the changelog-report-plugin, file-activity-report-plugin and > developer-activity-report-plugin) require the SCM URL to end in "/..." to be > able to produce output. > Fix: when creating the clientspec, only append "/..." if it is not already > there. > (I'm not sure if "p4 filelog" is invoked by this component or those other > report plugins.) > *Untested* patch attached. -- 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-114) Clientspec naming
[ http://jira.codehaus.org/browse/SCM-114?page=all ]
Emmanuel Venisse closed SCM-114:
> Clientspec naming
> -
>
> Key: SCM-114
> URL: http://jira.codehaus.org/browse/SCM-114
> Project: Maven SCM
> Type: Improvement
> Components: maven-scm-provider-perforce
> Versions: 1.0-beta-3
> Reporter: Mike Perham
> Assignee: Mike Perham
> Fix For: 1.0-beta-3
>
>
> Several people have expressed more than a passing interest in how the
> Perforce clientspec is named by Maven SCM. The name needs to be
> autogenerated and unique for each Continuum project build. Currently I am
> thinking something like:
> ${project}-${user}-${hostname}-mavenscm
> Emmannuel, does the SCM subsystem have access to the name of the project
> being built? If not, I can just use the name of the last directory in the
> SCM URL for the name of the project: //depot/projects/foobar would mean that
> ${project} = foobar.
> And just head off the inevitable question: you cannot set P4CLIENT for this
> because Continuum may build several different projects and they each need a
> unique clientspec.
--
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-113) Support persistent and transient clientspecs
[ http://jira.codehaus.org/browse/SCM-113?page=all ] Emmanuel Venisse closed SCM-113: > Support persistent and transient clientspecs > > > Key: SCM-113 > URL: http://jira.codehaus.org/browse/SCM-113 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-perforce > Versions: 1.0-beta-3 > Reporter: Mike Perham > Assignee: Mike Perham > Fix For: 1.0-beta-3 > > > Continuum needs a persistent clientspec because it needs to update a > project's source code and build it once an hour. On larger projects a > complete resync might take 10-20 minutes so it is necessary to keep a > clientspec around for that Continuum project build so syncs only take a few > seconds. > However, the Maven Release plugin may need to be used by tens or even > hundreds of developers to release any number of small modules. Currently > this would mean lots of clientspecs being created for the release checkout > which are reused very infrequently. Here I would prefer to create the > clientspec, do the checkout, build and then delete the clientspec. This is > what I term a transient clientspec. > The Perforce plugin would need to default to one mode and support some sort > of hint which tells it which mode to operate in. -- 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-148) specify flags to svn
[ http://jira.codehaus.org/browse/SCM-148?page=comments#action_57748 ] Emmanuel Venisse commented on SCM-148: -- Is it only for update command or all commands? > specify flags to svn > > > Key: SCM-148 > URL: http://jira.codehaus.org/browse/SCM-148 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: David Saff > Fix For: 1.0-beta-3 > > > I'd like an easy way to specify flags that should be passed to the svn > command when updating my project. For example, I'd like to pass the > --config-dir flag to svn, to redirect it to a different configuration > directory. -- 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-136) Make it possible to pay attention to .cvsrc
[ http://jira.codehaus.org/browse/SCM-136?page=all ] Emmanuel Venisse closed SCM-136: Assign To: Emmanuel Venisse Resolution: Fixed Done. > Make it possible to pay attention to .cvsrc > > > Key: SCM-136 > URL: http://jira.codehaus.org/browse/SCM-136 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-cvs > Versions: 1.0-beta-2 > Reporter: Matthew Beermann > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > There ought to be a way to tell the SCM plugin to obey the .cvsrc file. > Here's why: > I've had developers complain about empty directories showing up in their jar > endstates. Simple, I thought - just add "checkout -P" to my .cvsrc file. But, > if I'm reading > http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-providers/maven-scm-provider-cvs/src/main/java/org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutCommand.java?view=markup > correctly, the plugin will always ignore the .cvsrc file since it always > specifies the "-f" flag and doesn't allow arbitrary flags to be passed in. > I can understand the reasoning behind this behavior - there are certainly CVS > flags that would make Maven very unhappy - but there's also something to be > said for giving people enough rope to hang themselves with. All sorts of > important/useful settings (like compression) could be in their .cvsrc too. In > my case, at least, I don't see any other way to get it done. -- 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-136) Make it possible to pay attention to .cvsrc
[ http://jira.codehaus.org/browse/SCM-136?page=all ] Emmanuel Venisse updated SCM-136: - Component: maven-scm-provider-cvs > Make it possible to pay attention to .cvsrc > > > Key: SCM-136 > URL: http://jira.codehaus.org/browse/SCM-136 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-cvs > Versions: 1.0-beta-2 > Reporter: Matthew Beermann > Fix For: 1.0-beta-3 > > > There ought to be a way to tell the SCM plugin to obey the .cvsrc file. > Here's why: > I've had developers complain about empty directories showing up in their jar > endstates. Simple, I thought - just add "checkout -P" to my .cvsrc file. But, > if I'm reading > http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-providers/maven-scm-provider-cvs/src/main/java/org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutCommand.java?view=markup > correctly, the plugin will always ignore the .cvsrc file since it always > specifies the "-f" flag and doesn't allow arbitrary flags to be passed in. > I can understand the reasoning behind this behavior - there are certainly CVS > flags that would make Maven very unhappy - but there's also something to be > said for giving people enough rope to hang themselves with. All sorts of > important/useful settings (like compression) could be in their .cvsrc too. In > my case, at least, I don't see any other way to get it done. -- 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-151) Make it possible to define global cvs options
[ http://jira.codehaus.org/browse/SCM-151?page=all ] Emmanuel Venisse closed SCM-151: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Done. > Make it possible to define global cvs options > - > > Key: SCM-151 > URL: http://jira.codehaus.org/browse/SCM-151 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-cvs > Versions: 1.0-beta-3 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > -- 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-134) Set CVSROOT consistently in all commands in cvs-provider
[ http://jira.codehaus.org/browse/SCM-134?page=all ] Emmanuel Venisse closed SCM-134: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Done by CvsCommandUtils class > Set CVSROOT consistently in all commands in cvs-provider > > > Key: SCM-134 > URL: http://jira.codehaus.org/browse/SCM-134 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-beta-3 > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-134.patch > > > Most of the commands in the cvs provider use the command line argument "-d > CVSROOT", but not all of them. > The attached patch adds "-d CVSROOT" to these commands: > * CvsDiffCommand > * CvsStatusCommand > * CvsUpdateCommand > This change also made it necessary to alter the CvsUpdateCommandTest so that > it works on Windows. > That test now uses CvsScmTestUtils.getScmUrl() to get an scmUrl. > CvsScmTestUtils.getScmUrl() has been corrected to use the vertical bar "|" as > the delimiter in all places of the scm url. -- 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-150) Start pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-150?page=comments#action_57696 ] Emmanuel Venisse commented on SCM-150: -- I can't implement all commands for 1.0-beta-3, so the start will contain only the changelog command. SCM-10 will be all other commands. > Start pure java cvs provider > > > Key: SCM-150 > URL: http://jira.codehaus.org/browse/SCM-150 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-cvs > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > required by changelo plugin for backward compatibility -- 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-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Emmanuel Venisse closed SCM-124: Resolution: Fixed Applied. Thanks. > StarteamChangeLogConsumerTest does not work if locale is not en or fr > - > > Key: SCM-124 > URL: http://jira.codehaus.org/browse/SCM-124 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-124.patch > > > The testcase StarteamChangeLogConsumerTest makes assumptions about the user's > locale that are not always true. > Lines 45-52 uses the default locale and if a suitable changelog for that > locale is not found, it defaults to using the English changelog file. This > works well for English and French which have changelog files. But it does not > work for other locales that use a different dateformat than English, i.e most > of Europe. > The problem is that the class StarteamChangeLogConsumer has a private > instance variable of SimpleDateFormat called localFormat. This variable can > not be set from outside the class. On line 390 localFormat is used to parse > dates. This will fail if the user has a different locale than the one being > used in the logfile being parsed. I imagine that it is common (at least not > uncommon) to have different locales on the server and the client. > So the locale used in the StarteamChangeLogConsumer needs to be set to the > locale used by the *server* and not the *client*. A simple getter/setter > would do the trick. The locale would need to be configurable in some way so > that the user can set the locale that is used by his/her server. > The reason I stumbled upon this was when I tried to do "mvn test" for > maven-scm. It produced this stacktrace: > ... > [INFO] > > [INFO] Building Maven SCM Starteam Provider > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 25 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 22 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports > --- > T E S T S > --- > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > Added: ./maven.xml > Added: ./target/checkout/maven.xml > Added: ./target/checkout/project.properties > Added: ./target/checkout/project.xml > Added: ./target/checkout/bootstrap/maven.xml > Added: ./target/checkout/bootstrap/project.properties > Added: ./target/checkout/bootstrap/project.xml > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest > [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [ERROR] ParseException Caught > java.text.ParseException: Unparseable date: "4/21/04 1:05:00 PM PDT" > at java.text.DateFormat.parse(DateFormat.java:335) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.process
[jira] Closed: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Emmanuel Venisse closed SCM-124: Assign To: Emmanuel Venisse Resolution: Fixed Fixed. I've tested with : MAVEN_OPTS=-Duser.language=de -Duser.country=DE > StarteamChangeLogConsumerTest does not work if locale is not en or fr > - > > Key: SCM-124 > URL: http://jira.codehaus.org/browse/SCM-124 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > The testcase StarteamChangeLogConsumerTest makes assumptions about the user's > locale that are not always true. > Lines 45-52 uses the default locale and if a suitable changelog for that > locale is not found, it defaults to using the English changelog file. This > works well for English and French which have changelog files. But it does not > work for other locales that use a different dateformat than English, i.e most > of Europe. > The problem is that the class StarteamChangeLogConsumer has a private > instance variable of SimpleDateFormat called localFormat. This variable can > not be set from outside the class. On line 390 localFormat is used to parse > dates. This will fail if the user has a different locale than the one being > used in the logfile being parsed. I imagine that it is common (at least not > uncommon) to have different locales on the server and the client. > So the locale used in the StarteamChangeLogConsumer needs to be set to the > locale used by the *server* and not the *client*. A simple getter/setter > would do the trick. The locale would need to be configurable in some way so > that the user can set the locale that is used by his/her server. > The reason I stumbled upon this was when I tried to do "mvn test" for > maven-scm. It produced this stacktrace: > ... > [INFO] > > [INFO] Building Maven SCM Starteam Provider > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 25 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 22 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports > --- > T E S T S > --- > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > Added: ./maven.xml > Added: ./target/checkout/maven.xml > Added: ./target/checkout/project.properties > Added: ./target/checkout/project.xml > Added: ./target/checkout/bootstrap/maven.xml > Added: ./target/checkout/bootstrap/project.properties > Added: ./target/checkout/bootstrap/project.xml > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest > [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [ERROR] ParseException Caught > java.text.ParseException: Unparseable date: "4/21/04 1:05:00 PM PDT" > at java.text.DateFormat.parse(DateFormat.java:335) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) > at > org.apache.maven.scm.provide
[jira] Closed: (SCM-130) scm:validate should not require a project
[ http://jira.codehaus.org/browse/SCM-130?page=all ] Emmanuel Venisse closed SCM-130: Assign To: Emmanuel Venisse Resolution: Fixed Done. > scm:validate should not require a project > - > > Key: SCM-130 > URL: http://jira.codehaus.org/browse/SCM-130 > Project: Maven SCM > Type: Improvement > Versions: 1.0-beta-2 > Environment: xp, cvs, starteam > Reporter: Dan Tran > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > We should be able to run scm:validate any where as long as we can passin > -DconnectionUrl -- 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-150) Start pure java cvs provider
[ http://jira.codehaus.org/browse/SCM-150?page=all ] Emmanuel Venisse updated SCM-150: - Assign To: Emmanuel Venisse Fix Version: 1.0-beta-3 > Start pure java cvs provider > > > Key: SCM-150 > URL: http://jira.codehaus.org/browse/SCM-150 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-cvs > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > required by changelo plugin for backward compatibility -- 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-150) Start pure java cvs provider
Start pure java cvs provider Key: SCM-150 URL: http://jira.codehaus.org/browse/SCM-150 Project: Maven SCM Type: New Feature Components: maven-scm-provider-cvs Reporter: Emmanuel Venisse Fix For: 1.0-beta-3 required by changelo plugin for backward compatibility -- 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-21) separate revision and tag handling
[ http://jira.codehaus.org/browse/SCM-21?page=all ]
Emmanuel Venisse updated SCM-21:
Fix Version: (was: 1.0-beta-3)
> separate revision and tag handling
> --
>
> Key: SCM-21
> URL: http://jira.codehaus.org/browse/SCM-21
> Project: Maven SCM
> Type: Task
> Components: maven-scm-api
> Reporter: Brett Porter
>
>
> while in CVS revision# and tag are handled in the same way, the concepts can
> be separated and will make other SCMs easier.
> for example, in subversion, valid revisions are:
> rev#
> HEAD
> BASE
> COMMITTED
> PREV
> {DATE}
> tags are normal checkouts from a different base.
> In CVS, revisions are:
> rev# (per file only really makes sense here, but can apply to several)
> HEAD
> SOME_BRANCH_TAG
> {DATE}
--
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-117) Add parameters to scm configuration element
[ http://jira.codehaus.org/browse/SCM-117?page=all ] Emmanuel Venisse updated SCM-117: - Fix Version: (was: 1.0-beta-3) > Add parameters to scm configuration element > --- > > Key: SCM-117 > URL: http://jira.codehaus.org/browse/SCM-117 > Project: Maven SCM > Type: Wish > Components: maven-scm-provider-starteam > Versions: 1.0-beta-2 > Reporter: Aviran Mordo > Assignee: Dan Tran > > > It would be very nice to have the ability to add parameters to the scm > element. For instance to add parameter to always force checkout. for instance > in Starteam I would like to add -o so every time stcmd is called the > parameters will be concatenated to the command line -- 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-beta-3) 1.0 > 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 > > > 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-133) Merge redundant repository classes
[ http://jira.codehaus.org/browse/SCM-133?page=all ] Emmanuel Venisse updated SCM-133: - Fix Version: (was: 1.0-beta-3) > Merge redundant repository classes > -- > > Key: SCM-133 > URL: http://jira.codehaus.org/browse/SCM-133 > Project: Maven SCM > Type: Improvement > Components: maven-scm-api > Versions: 1.0-beta-2 > Reporter: Mike Perham > > > Currently there are: > com.apache.maven.scm.repository.ScmRepository > com.apache.maven.scm.provider.ScmProviderRepository > The comment at the top of the former says: > * @todo clarify need - should be able to merge with ScmProviderRepository? -- 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-57) m2 maven-scm-plugin should use the same configurations/properties with M1 plugin
[ http://jira.codehaus.org/browse/SCM-57?page=all ] Emmanuel Venisse updated SCM-57: Fix Version: (was: 1.0-beta-3) > m2 maven-scm-plugin should use the same configurations/properties with M1 > plugin > > > Key: SCM-57 > URL: http://jira.codehaus.org/browse/SCM-57 > Project: Maven SCM > Type: Bug > Components: maven-plugin > Versions: 1.0-alpha-3 > Environment: xp > Reporter: Dan Tran > > > I think m2 should try to make scm plugin configuration compatible with m2 -- 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-beta-3) 1.0 > 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 > > > 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] Closed: (SCM-127) Starteam no revision comments
[ http://jira.codehaus.org/browse/SCM-127?page=all ] Emmanuel Venisse closed SCM-127: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 It was a bug in maven-scm-api > Starteam no revision comments > - > > Key: SCM-127 > URL: http://jira.codehaus.org/browse/SCM-127 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continumm on Linux > Reporter: Bob Herrmann > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0-beta-3 > > > I'm using continuum to build a project from Starteam. Continuum shows what > files changed in Starteam from build to but not the entered revision comments > for why the file was changed. Emmanuel Venisse said that this was probably a > bug in the starteam provider, and asked that I file a bug here. -- 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-148) specify flags to svn
[ http://jira.codehaus.org/browse/SCM-148?page=all ] Emmanuel Venisse updated SCM-148: - Fix Version: 1.0-beta-3 > specify flags to svn > > > Key: SCM-148 > URL: http://jira.codehaus.org/browse/SCM-148 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: David Saff > Fix For: 1.0-beta-3 > > > I'd like an easy way to specify flags that should be passed to the svn > command when updating my project. For example, I'd like to pass the > --config-dir flag to svn, to redirect it to a different configuration > directory. -- 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-149) Start VSS provider
[ http://jira.codehaus.org/browse/SCM-149?page=all ] Emmanuel Venisse closed SCM-149: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Started with changelog command > Start VSS provider > -- > > Key: SCM-149 > URL: http://jira.codehaus.org/browse/SCM-149 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-vss > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > -- 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-149) Start VSS provider
Start VSS provider -- Key: SCM-149 URL: http://jira.codehaus.org/browse/SCM-149 Project: Maven SCM Type: New Feature Components: maven-scm-provider-vss Reporter: Emmanuel Venisse -- 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-131) mvn scm:validate does not validate the developerConnection in the pom
[ http://jira.codehaus.org/browse/SCM-131?page=all ]
Emmanuel Venisse updated SCM-131:
-
Fix Version: 1.0-beta-3
> mvn scm:validate does not validate the developerConnection in the pom
> -
>
> Key: SCM-131
> URL: http://jira.codehaus.org/browse/SCM-131
> Project: Maven SCM
> Type: Bug
> Components: maven-plugin
> Reporter: Dennis Lundberg
> Fix For: 1.0-beta-3
> Attachments: SCM-131.patch
>
>
> There are a couple of reasons for this, in ValidateMojo:
> # The check to see if the scmDeveloperConnection is not null is done on the
> scmConnection
> # The @parameter definitions are wrong for both the the scmConnection and
> scmDeveloperConnection
> The check for scmConnection is never run either because of of the wrong
> @parameter definitions. But the actual value from the pom is normally checked
> anyway because the default-value for connectionUrl in AbstractScmMojo is
> ${pom.scm.connection}. But if you run it like this:
> mvn scm:validate -DconnectionUrl=invalidScmUrl
> the value of pom.scm.connection will not be checked.
> The supplied patch fixes these problems and logs an extra error the tells the
> user the value of the invalid scm connection url, to help resolve the problem.
--
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-13) Investigate pure Java SVN interface
[ http://jira.codehaus.org/browse/SCM-13?page=all ] Emmanuel Venisse updated SCM-13: Fix Version: 1.0 > Investigate pure Java SVN interface > --- > > Key: SCM-13 > URL: http://jira.codehaus.org/browse/SCM-13 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-svn > Reporter: Brett Porter > Fix For: 1.0 > Attachments: SCM-13-maven-scm-api.patch, > SCM-13-maven-scm-manager-plexus.patch, SCM-13-maven-scm-plugin.patch, > SCM-13-maven-scm-provider-svn.tar.gz, ch.ethz.ganymed.tar.gz, > tmate.org.javasvn.tar.gz > > > There is this: http://tmate.org/svn/ > I'd say javahl is out because it requires native binaries. -- 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-85) Allow svn username/password to be set in servers section of settings.xml
[ http://jira.codehaus.org/browse/SCM-85?page=all ] Emmanuel Venisse updated SCM-85: Fix Version: 1.0-beta-3 > Allow svn username/password to be set in servers section of settings.xml > > > Key: SCM-85 > URL: http://jira.codehaus.org/browse/SCM-85 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-svn > Reporter: Micah Schehl > Fix For: 1.0-beta-3 > Attachments: MNG-85-maven-scm.patch, SCM-85.patch > > > Allow developers to have their own subversion username/password set in > settings.xml.Also, this would prevent having to use the web setup to > enter username/password in Continuum since the info would be in settings.xml. -- 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-38) Ability to assign an issue tracking to add, lock, and checkin
[ http://jira.codehaus.org/browse/SCM-38?page=comments#action_57650 ] Emmanuel Venisse commented on SCM-38: - Dan Tran, Do you want work on it? > Ability to assign an issue tracking to add, lock, and checkin > - > > Key: SCM-38 > URL: http://jira.codehaus.org/browse/SCM-38 > Project: Maven SCM > Type: New Feature > Components: maven-scm-api > Versions: 1.0-alpha-1 > Environment: xp, maven 1.0.2 > Reporter: Dan Tran > > > Clearcase and starteam (if configured) insist to have an associate issue > id ( ie activity in clearcase, CR/activity/task in starteam) during lock, > add, and checkin commands. > Suggest to add "issue" argument for those commands in maven-scm-api interface -- 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-beta-3) 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-beta-3 > Reporter: Mike Perham > Fix For: 1.0 > > > 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-29) test with CVS NT
[ http://jira.codehaus.org/browse/SCM-29?page=all ] Emmanuel Venisse updated SCM-29: Fix Version: 1.0 > test with CVS NT > > > Key: SCM-29 > URL: http://jira.codehaus.org/browse/SCM-29 > Project: Maven SCM > Type: Test > Components: maven-scm-provider-cvs > Reporter: Brett Porter > Fix For: 1.0 > > > Vincent reported test failures on CVS NT... test it and fix if required. -- 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-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=all ] Emmanuel Venisse updated SCM-124: - Fix Version: 1.0-beta-3 > StarteamChangeLogConsumerTest does not work if locale is not en or fr > - > > Key: SCM-124 > URL: http://jira.codehaus.org/browse/SCM-124 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale > Reporter: Dennis Lundberg > Fix For: 1.0-beta-3 > > > The testcase StarteamChangeLogConsumerTest makes assumptions about the user's > locale that are not always true. > Lines 45-52 uses the default locale and if a suitable changelog for that > locale is not found, it defaults to using the English changelog file. This > works well for English and French which have changelog files. But it does not > work for other locales that use a different dateformat than English, i.e most > of Europe. > The problem is that the class StarteamChangeLogConsumer has a private > instance variable of SimpleDateFormat called localFormat. This variable can > not be set from outside the class. On line 390 localFormat is used to parse > dates. This will fail if the user has a different locale than the one being > used in the logfile being parsed. I imagine that it is common (at least not > uncommon) to have different locales on the server and the client. > So the locale used in the StarteamChangeLogConsumer needs to be set to the > locale used by the *server* and not the *client*. A simple getter/setter > would do the trick. The locale would need to be configurable in some way so > that the user can set the locale that is used by his/her server. > The reason I stumbled upon this was when I tried to do "mvn test" for > maven-scm. It produced this stacktrace: > ... > [INFO] > > [INFO] Building Maven SCM Starteam Provider > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 25 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 22 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports > --- > T E S T S > --- > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > Added: ./maven.xml > Added: ./target/checkout/maven.xml > Added: ./target/checkout/project.properties > Added: ./target/checkout/project.xml > Added: ./target/checkout/bootstrap/maven.xml > Added: ./target/checkout/bootstrap/project.properties > Added: ./target/checkout/bootstrap/project.xml > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest > [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [ERROR] ParseException Caught > java.text.ParseException: Unparseable date: "4/21/04 1:05:00 PM PDT" > at java.text.DateFormat.parse(DateFormat.java:335) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.processGetAuthor(StarteamChangeLogConsumer.java:281 > at > org.apache.maven
[jira] Commented: (SCM-124) StarteamChangeLogConsumerTest does not work if locale is not en or fr
[ http://jira.codehaus.org/browse/SCM-124?page=comments#action_57649 ] Emmanuel Venisse commented on SCM-124: -- Dennis, Can you check if this test is ok now? > StarteamChangeLogConsumerTest does not work if locale is not en or fr > - > > Key: SCM-124 > URL: http://jira.codehaus.org/browse/SCM-124 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: Maven 2.0.1, JDK 1.4.2_09, Win XP Pro, Swedish locale > Reporter: Dennis Lundberg > Fix For: 1.0-beta-3 > > > The testcase StarteamChangeLogConsumerTest makes assumptions about the user's > locale that are not always true. > Lines 45-52 uses the default locale and if a suitable changelog for that > locale is not found, it defaults to using the English changelog file. This > works well for English and French which have changelog files. But it does not > work for other locales that use a different dateformat than English, i.e most > of Europe. > The problem is that the class StarteamChangeLogConsumer has a private > instance variable of SimpleDateFormat called localFormat. This variable can > not be set from outside the class. On line 390 localFormat is used to parse > dates. This will fail if the user has a different locale than the one being > used in the logfile being parsed. I imagine that it is common (at least not > uncommon) to have different locales on the server and the client. > So the locale used in the StarteamChangeLogConsumer needs to be set to the > locale used by the *server* and not the *client*. A simple getter/setter > would do the trick. The locale would need to be configurable in some way so > that the user can set the locale that is used by his/her server. > The reason I stumbled upon this was when I tried to do "mvn test" for > maven-scm. It produced this stacktrace: > ... > [INFO] > > [INFO] Building Maven SCM Starteam Provider > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > Compiling 25 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\classes > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 22 source files to > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target\test-classes > [INFO] [surefire:test] > [INFO] Setting reports dir: > G:\svn\maven-scm\maven-scm-providers\maven-scm-provider-starteam\target/surefire-reports > --- > T E S T S > --- > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddCommandTest > [surefire] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > Added: ./maven.xml > Added: ./target/checkout/maven.xml > Added: ./target/checkout/project.properties > Added: ./target/checkout/project.xml > Added: ./target/checkout/bootstrap/maven.xml > Added: ./target/checkout/bootstrap/project.properties > Added: ./target/checkout/bootstrap/project.xml > [surefire] Running > org.apache.maven.scm.provider.starteam.command.add.StarteamAddConsumerTest > [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,03 sec > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [WARNING] Your scm URL use a deprecated format. The new format is > :[username[:[EMAIL PROTECTED]:port:/projectName/[viewName/][folderHiearchy/] > [surefire] Running > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogCommandTest > [surefire] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,02 sec > [ERROR] ParseException Caught > java.text.ParseException: Unparseable date: "4/21/04 1:05:00 PM PDT" > at java.text.DateFormat.parse(DateFormat.java:335) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.parseDate(StarteamChangeLogConsumer.java:390) > at > org.apache.maven.scm.provider.starteam.command.changelog.StarteamChangeLogConsumer.processGetAuthor(StarteamChangeLogCon
[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] Closed: (SCM-35) Catch InterruptedException when executing the external process
[ http://jira.codehaus.org/browse/SCM-35?page=all ] Emmanuel Venisse closed SCM-35: --- Resolution: Fixed Already done since a long time. It's catched in CommandLineUtils > Catch InterruptedException when executing the external process > -- > > Key: SCM-35 > URL: http://jira.codehaus.org/browse/SCM-35 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-local, maven-scm-provider-svn, > maven-scm-api, maven-scm-provider-cvs, maven-scm-provider-starteam, > maven-scm-provider-clearcase, maven-scm-provider-perforce, > maven-scm-provider-vss > Reporter: Trygve Laugstol > > > This is useful for more graceful handling of exception when you want to > terminate the currently executing scm command. -- 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-22) Support properties based configuration for VSS provider
[ http://jira.codehaus.org/browse/SCM-22?page=all ] Emmanuel Venisse closed SCM-22: --- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Done. > Support properties based configuration for VSS provider > --- > > Key: SCM-22 > URL: http://jira.codehaus.org/browse/SCM-22 > Project: Maven SCM > Type: Wish > Components: maven-scm-provider-vss > Versions: 1.0-alpha-1 > Environment: Windows > Reporter: Troy Poppe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > The Microsoft VSS command-line utility, ss.exe, needs to be located so that a > proper command line can be built for execution. > Support the ability to pass the path to ss.exe via properties. -- 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-84) Develop VSS Provider for Maven-SCM
[ http://jira.codehaus.org/browse/SCM-84?page=comments#action_57430 ] Emmanuel Venisse commented on SCM-84: - Do you have done more work on this provider? > Develop VSS Provider for Maven-SCM > -- > > Key: SCM-84 > URL: http://jira.codehaus.org/browse/SCM-84 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-vss > Reporter: George Gastaldi > Attachments: maven-scm-provider-vss-unfinished.zip, > maven-scm-provider-vss.zip > > -- 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-143) New SCM Provider: Bazaar
[ http://jira.codehaus.org/browse/SCM-143?page=comments#action_57413 ] Emmanuel Venisse commented on SCM-143: -- Can you provide documentation of this provider for maven-scm site? All docs are in maven-scm-site > 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] Closed: (SCM-143) New SCM Provider: Bazaar
[ http://jira.codehaus.org/browse/SCM-143?page=all ] Emmanuel Venisse closed SCM-143: Resolution: Fixed Applied. Thanks. All tests works fine now for me on windows. It was an error in my bzr.bat > 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] Closed: (SCM-146) ClearCase mkview cannot be run without -vws switch
[ http://jira.codehaus.org/browse/SCM-146?page=all ] Emmanuel Venisse closed SCM-146: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Fixed. > ClearCase mkview cannot be run without -vws switch > -- > > Key: SCM-146 > URL: http://jira.codehaus.org/browse/SCM-146 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Versions: 1.0-beta-3 > Environment: Linux (via Continuum) > Reporter: Piotr Kosiorowski > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > Currently there is no way to run mkview command without -vws parameter > (except specifying ClearCase LT that turns on also other features). Such > invocation is required by our ClearCase installation. I suggest not to use > default value for view storage if none is specified in clearcase-settings > file. Introduction of other parameter was to control it was suggested on > mailing list. > -- 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-126) Check if change set is populated correctly
[ http://jira.codehaus.org/browse/SCM-126?page=all ] Emmanuel Venisse closed SCM-126: Resolution: Fixed Done. The pb was only with svn provider. > Check if change set is populated correctly > -- > > Key: SCM-126 > URL: http://jira.codehaus.org/browse/SCM-126 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-svn, maven-scm-provider-starteam, > maven-scm-provider-pvcs, maven-scm-provider-perforce, > maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-clearcase > Versions: 1.0-beta-2 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > It seems that isn't do correctly for all providers (except for cvs). > In Continuum we need these informations for build result page. -- 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-126) Check if change set is populated correctly
[ http://jira.codehaus.org/browse/SCM-126?page=comments#action_56622 ] Emmanuel Venisse commented on SCM-126: -- change set isn't populated correctly (at least for svn provider). For svn provider, file path is relative to working directory for update command and it's absolute path in repository for changelog command. So for the file pom.xml in /maven/scm/maven-scm-api/pom.xml, if command are run in maven-scm-api working-directory, file path is pom.xml for update command and /maven/scm/maven-scm-api.xml for changelog command. These two path are different string and the file isn't added in change set. > Check if change set is populated correctly > -- > > Key: SCM-126 > URL: http://jira.codehaus.org/browse/SCM-126 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-svn, maven-scm-provider-starteam, > maven-scm-provider-pvcs, maven-scm-provider-perforce, > maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-clearcase > Versions: 1.0-beta-2 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > It seems that isn't do correctly for all providers (except for cvs). > In Continuum we need these informations for build result page. -- 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-140) Refactoring clearcase-setting.xml loading
Refactoring clearcase-setting.xml loading - Key: SCM-140 URL: http://jira.codehaus.org/browse/SCM-140 Project: Maven SCM Type: Task Components: maven-scm-provider-clearcase Versions: 1.0-alpha-3 Reporter: Emmanuel Venisse Code is actually duplicated in checkout command and changelog command -- 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-140) Refactoring clearcase-setting.xml loading
[ http://jira.codehaus.org/browse/SCM-140?page=all ] Emmanuel Venisse updated SCM-140: - Version: (was: 1.0-alpha-3) 1.0-beta-3 Fix Version: 1.0-beta-3 > Refactoring clearcase-setting.xml loading > - > > Key: SCM-140 > URL: http://jira.codehaus.org/browse/SCM-140 > Project: Maven SCM > Type: Task > Components: maven-scm-provider-clearcase > Versions: 1.0-beta-3 > Reporter: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > Code is actually duplicated in checkout command and changelog command -- 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-135) Clearcase LT integration
[ http://jira.codehaus.org/browse/SCM-135?page=all ] Emmanuel Venisse closed SCM-135: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. Frederic, can you provide a patch for documentation of settings.xml? > Clearcase LT integration > > > Key: SCM-135 > URL: http://jira.codehaus.org/browse/SCM-135 > Project: Maven SCM > Type: New Feature > Components: maven-scm-provider-clearcase > Versions: 1.0-beta-3 > Environment: ClearCase LT version > Windows Server > Reporter: Frederic Mura > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-135-maven-scm-provider-clearcase.patch, > SCM-135-maven-scm-provider-clearcase.patch, maven-scm-provider-clearcase.zip > > > Add a new setting entry in the file ".scm/clearcase-settings": > > \\ORACLE\ClearCaseStorage\Views\PDS > *true* > > to support the ClearCase LT application. > The differences between the ClearCase _Full_ and the ClearCase LT are: > Checkout : cleartool mkview does not support the _-vws_ attribut > changelog : cleartool lhistory does not support the attributes _-fmt_ > and _-since_ > Otherwise all other command are same. > As attachment the clearcase provider source file. -- 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_56596 ] Emmanuel Venisse commented on SCM-139: -- - isValid(): I'd prefer an other name like isValidGeneralFormat - remove "void validate( scmUrl ) - getSeparator() : I prefer a String as returned value > 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: 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
[jira] Closed: (SCM-138) clearcase-settings.xml is been searched for in the wrong dir
[ http://jira.codehaus.org/browse/SCM-138?page=all ] Emmanuel Venisse closed SCM-138: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Done. > clearcase-settings.xml is been searched for in the wrong dir > > > Key: SCM-138 > URL: http://jira.codehaus.org/browse/SCM-138 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Reporter: Wim Deblauwe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > There is a problem in the class: > org.apache.maven.scm.provider.clearcase.command.checkout.ClearCaseCheckOutCommand, > the code is: > File scmUserDir = new File( System.getProperty( "user.dir" ), ".scm" ); > File settingsFile = new File( scmUserDir, "clearcase-settings.xml" ); > In that code user.dir should be changed to user.home > regards, > Wim -- 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-123) scm plugin ignores -Dusername for CSV provider
[ http://jira.codehaus.org/browse/SCM-123?page=all ] Emmanuel Venisse closed SCM-123: Assign To: Emmanuel Venisse Resolution: Fixed Fixed > scm plugin ignores -Dusername for CSV provider > -- > > Key: SCM-123 > URL: http://jira.codehaus.org/browse/SCM-123 > Project: Maven SCM > Type: Bug > Components: maven-plugin > Versions: 1.0-beta-2 > Environment: xp, cvs > Reporter: Dan Tran > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-123-docs.patch > > > mvn scm:validate -DconnectionUrl=scm:cvs:pserver:host:/cvs:module -X > -Dusername=joe > fails with > [DEBUG] (f) basedir = C:\dev\maven\src\scm > [DEBUG] (f) connectionUrl = scm:cvs:pserver:host:/cvs:module > [DEBUG] (f) settings = [EMAIL PROTECTED] > [DEBUG] (f) username = joe > [DEBUG] -- end configuration -- > [INFO] [scm:validate] > [ERROR] Error scm url connection (connectionUrl) validation failed : > [ERROR] The userhost part must be on the form: @. > is it intended? > Found this problem when looking at MNG-1783 -- 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-1) Publish site for 1.0
[ http://jira.codehaus.org/browse/SCM-1?page=all ] Emmanuel Venisse closed SCM-1: -- Resolution: Fixed Applied. Thanks > Publish site for 1.0 > > > Key: SCM-1 > URL: http://jira.codehaus.org/browse/SCM-1 > Project: Maven SCM > Type: Task > Versions: 1.0-alpha-1 > Reporter: Jason van Zyl > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-1.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] Closed: (SCM-112) Broken links to mail-archives
[ http://jira.codehaus.org/browse/SCM-112?page=all ] Emmanuel Venisse closed SCM-112: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. Thanks > Broken links to mail-archives > - > > Key: SCM-112 > URL: http://jira.codehaus.org/browse/SCM-112 > Project: Maven SCM > Type: Bug > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Priority: Minor > Fix For: 1.0-beta-3 > Attachments: mail-archive.patch > > > The links to the mail-archives are broken. I've attached a patch that fixes > this in the master pom.xml. -- 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-106) Validation of scm url fails because of ambiquities between source code and site documentation
[ http://jira.codehaus.org/browse/SCM-106?page=all ] Emmanuel Venisse closed SCM-106: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. Thanks. > Validation of scm url fails because of ambiquities between source code and > site documentation > - > > Key: SCM-106 > URL: http://jira.codehaus.org/browse/SCM-106 > Project: Maven SCM > Type: Bug > Components: maven-scm-api > Reporter: Dennis Lundberg > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: SCM-106.patch > > > I am trying out Continuum and am tracking down the cause of why I get an > error regarding the scm url that I provide when adding an ant project. This > has led me here. I copied the scm url from my maven 1 project.xml and got a > very breif error message telling me to enter a valid scm url. > My scm url looks like this: > scm|cvs|pserver|[EMAIL PROTECTED]|C:/Program/cvsnt/repositories|project-name > This works just fine using maven 1. > These two files are involved in this: > maven-scm-api/src/main/java/org/apache/maven/scm/manager/AbstractScmManager.java > maven-scm-site/src/site/apt/cvs.apt > AbstractScmManager.java has the following error message declared: > private final static String ILLEGAL_SCM_URL = "The scm url must be on the > form " > + "'scm: provider>' " > + "where can be > either ':' or '|'."; > which explains how a correct scm url should look. > cvs.apt on the other hand does not have this explanation. It does say: > For all URLs below, we use a colon (:) as separator. If you use a colon for > one of the variables (e.g. a windows path), then use a pipe (|) as separator. > Then follows a bunch of examples, none of which use pipe (|) as a separator. > So to conclude: Continuum uses validateScmRepository(String scmUrl) and maven > scm flags my scm url as invalid, but the docs for the urls are not really > clear about what a delimiter/separator is and where they are in the scm url. > Asuming that the source code is correct, the the docs need updating to > reflect this. There should also be an example using pipe as a separator. If > someone can confirm this I can write a patch for the docs. -- 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-101) Clean scm url in AbstractScmManager when scmurl contains "../"
[ http://jira.codehaus.org/browse/SCM-101?page=all ] Emmanuel Venisse closed SCM-101: Assign To: Emmanuel Venisse Resolution: Fixed Fixed. > Clean scm url in AbstractScmManager when scmurl contains "../" > -- > > Key: SCM-101 > URL: http://jira.codehaus.org/browse/SCM-101 > Project: Maven SCM > Type: Improvement > Components: maven-scm-api > Versions: 1.0-beta-1 > Reporter: Emmanuel Venisse > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > scm url like this scm:provider:path_to_repository/directory1/../directory2 > must be clean to scm:provider:path_to_repository/directory2 before to run scm > commands -- 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-123) scm plugin ignores -Dusername for CSV provider
[ http://jira.codehaus.org/browse/SCM-123?page=comments#action_55600 ] Emmanuel Venisse commented on SCM-123: -- you'll can define username in settings.xml like other provider, but it isn't part of maven-scm. > scm plugin ignores -Dusername for CSV provider > -- > > Key: SCM-123 > URL: http://jira.codehaus.org/browse/SCM-123 > Project: Maven SCM > Type: Bug > Components: maven-plugin > Versions: 1.0-beta-2 > Environment: xp, cvs > Reporter: Dan Tran > Fix For: 1.0-beta-3 > Attachments: SCM-123-docs.patch > > > mvn scm:validate -DconnectionUrl=scm:cvs:pserver:host:/cvs:module -X > -Dusername=joe > fails with > [DEBUG] (f) basedir = C:\dev\maven\src\scm > [DEBUG] (f) connectionUrl = scm:cvs:pserver:host:/cvs:module > [DEBUG] (f) settings = [EMAIL PROTECTED] > [DEBUG] (f) username = joe > [DEBUG] -- end configuration -- > [INFO] [scm:validate] > [ERROR] Error scm url connection (connectionUrl) validation failed : > [ERROR] The userhost part must be on the form: @. > is it intended? > Found this problem when looking at MNG-1783 -- 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-127) Starteam no revision comments
[ http://jira.codehaus.org/browse/SCM-127?page=comments#action_55277 ] Emmanuel Venisse commented on SCM-127: -- Strange, we use maven-scm api in continuum to display the change set. It works fine with cvs, so i think it's a pb in maven-scm. We have the same pb with svn. > Starteam no revision comments > - > > Key: SCM-127 > URL: http://jira.codehaus.org/browse/SCM-127 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-starteam > Environment: continumm on Linux > Reporter: Bob Herrmann > Priority: Minor > > > I'm using continuum to build a project from Starteam. Continuum shows what > files changed in Starteam from build to but not the entered revision comments > for why the file was changed. Emmanuel Venisse said that this was probably a > bug in the starteam provider, and asked that I file a bug here. -- 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-129) maven-release-plugin's checkForLocalModifications fails when there is non scm files the project
[ http://jira.codehaus.org/browse/SCM-129?page=comments#action_55275 ] Emmanuel Venisse commented on SCM-129: -- "?" status can be removed if you put files in cvs ignore list > maven-release-plugin's checkForLocalModifications fails when there is non scm > files the project > --- > > Key: SCM-129 > URL: http://jira.codehaus.org/browse/SCM-129 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-beta-3 > Environment: xp, cvs, latest maven-release-snapshot snaphot > Reporter: Dan Tran > Fix For: 1.0-beta-3 > > > when there are local files ( non scm files ) in the project, it becomes > unknow files when release plugin perform scm:status > and there for release:prepare will fail. > Is there a way for cvs provider to ignore those files so that release plugin > will be happy? > The word around is to do a clean checkout before release:prepare. -- 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-120) ClearCase Changelog test failure
[ http://jira.codehaus.org/browse/SCM-120?page=comments#action_54867 ] Emmanuel Venisse commented on SCM-120: -- mike, you can apply your patch and close this issue > ClearCase Changelog test failure > > > Key: SCM-120 > URL: http://jira.codehaus.org/browse/SCM-120 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-clearcase > Versions: 1.0-beta-3 > Reporter: mike perham > Fix For: 1.0-beta-3 > > > junit.framework.ComparisonFailure: expected:<...10...> but was:<...09...> > at junit.framework.Assert.assertEquals(Assert.java:81) > at junit.framework.Assert.assertEquals(Assert.java:87) > at > org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommandTest.testCommandLine(ClearCaseChangeLogCommandTest.java:97) > at > org.apache.maven.scm.provider.clearcase.command.changelog.ClearCaseChangeLogCommandTest.testGetCommandLineWithStartDate(ClearCaseChangeLogCommandTest.java:69) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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-126) Check if change set is populated correctly
Check if change set is populated correctly -- Key: SCM-126 URL: http://jira.codehaus.org/browse/SCM-126 Project: Maven SCM Type: Bug Components: maven-scm-provider-svn, maven-scm-provider-starteam, maven-scm-provider-pvcs, maven-scm-provider-perforce, maven-scm-provider-local, maven-scm-provider-cvs, maven-scm-provider-clearcase Versions: 1.0-beta-2 Reporter: Emmanuel Venisse Fix For: 1.0-beta-3 It seems that isn't do correctly for all providers (except for cvs). In Continuum we need these informations for build result page. -- 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-123) scm plugin ignores -Dusername for CSV provider
[ http://jira.codehaus.org/browse/SCM-123?page=comments#action_54406 ] Emmanuel Venisse commented on SCM-123: -- we'll allow users to define username in ScmRepository like other providers. It isn't recommended because username can be ommitted but some users need it. > scm plugin ignores -Dusername for CSV provider > -- > > Key: SCM-123 > URL: http://jira.codehaus.org/browse/SCM-123 > Project: Maven SCM > Type: Bug > Components: maven-plugin > Versions: 1.0-beta-2 > Environment: xp, cvs > Reporter: Dan Tran > Fix For: 1.0-beta-3 > Attachments: SCM-123-docs.patch > > > mvn scm:validate -DconnectionUrl=scm:cvs:pserver:host:/cvs:module -X > -Dusername=joe > fails with > [DEBUG] (f) basedir = C:\dev\maven\src\scm > [DEBUG] (f) connectionUrl = scm:cvs:pserver:host:/cvs:module > [DEBUG] (f) settings = [EMAIL PROTECTED] > [DEBUG] (f) username = joe > [DEBUG] -- end configuration -- > [INFO] [scm:validate] > [ERROR] Error scm url connection (connectionUrl) validation failed : > [ERROR] The userhost part must be on the form: @. > is it intended? > Found this problem when looking at MNG-1783 -- 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-125) Add interpretations of the "M" and "?" states for the CVS provider.
[ http://jira.codehaus.org/browse/SCM-125?page=all ] Emmanuel Venisse closed SCM-125: Assign To: Emmanuel Venisse Resolution: Fixed Fixed. > Add interpretations of the "M" and "?" states for the CVS provider. > --- > > Key: SCM-125 > URL: http://jira.codehaus.org/browse/SCM-125 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-cvs > Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-alpha-3, 1.0-alpha-4, 1.0-beta-1, > 1.0-beta-2 > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > > > I'm getting output like this: > ScmManager - ? allOldProcesses > ScmManager - Unknown status: '? '. > ScmManager - ? allProcesses > ScmManager - Unknown status: '? '. > ScmManager - ? target > ScmManager - Unknown status: '? '. > ScmManager - M > src/test-resources/kapaks-service-memory/1409521557.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1442081167.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1559246416.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1579687954.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1633409660.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1778550378.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/1836083304.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/2055859435.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/3010364852.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/3030806390.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/384964868.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/41596879.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/459128112.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/604740999.xml > ScmManager - Unknown status: 'M '. > ScmManager - M > src/test-resources/kapaks-service-memory/9037269.xml > ScmManager - Unknown status: 'M '. -- 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-115) log files should not show clear text password for perforce repository access
[ http://jira.codehaus.org/browse/SCM-115?page=all ] Emmanuel Venisse closed SCM-115: > log files should not show clear text password for perforce repository access > > > Key: SCM-115 > URL: http://jira.codehaus.org/browse/SCM-115 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0-beta-2 > Reporter: Mark Richters > Assignee: mike perham > Fix For: 1.0-beta-3 > Attachments: password.patch.txt > > > logs/wrapper.log contains entries like this: > [Thread-1] DEBUG ScmManager - Executing p4 -u mr -P > mypassword -cmyclient sync ... > It should not show mypassword in clear text (see also CONTINUUM-394). -- 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-118) detect and repair svn problems by running svn cleanup
detect and repair svn problems by running svn cleanup - Key: SCM-118 URL: http://jira.codehaus.org/browse/SCM-118 Project: Maven SCM Type: Bug Components: maven-scm-provider-svn Versions: 1.0-beta-2 Reporter: Emmanuel Venisse Fix For: 1.0-beta-3 -- 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-111) perforce: checkout doesn't work at all
[ http://jira.codehaus.org/browse/SCM-111?page=all ] Emmanuel Venisse closed SCM-111: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-3 Applied. > perforce: checkout doesn't work at all > -- > > Key: SCM-111 > URL: http://jira.codehaus.org/browse/SCM-111 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-perforce > Versions: 1.0-beta-2 > Environment: winX, maven 2, continuum > Reporter: skylab > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-3 > Attachments: svndiff.txt > > > When checking out any project, e. g. using 'continuum' 1.0.2, it stops > without any further explanation. > I think the bug can be found in the method > org...checkout.PerforceCheckOutCommand.createClientspec(). > You can see the class here: > http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-providers/maven-scm-provider-perforce/src/main/java/org/apache/maven/scm/provider/perforce/command/checkout/PerforceCheckOutCommand.java?rev=349907&view=markup > This results in an additional NEWLINE in the spec of a (new) client workspace > - after 'Root: ' > It should be > Client: any-clientspecname > Root: d:/workdir > View: > //repopath/... //clientspecName/... > please, look at the attached diff. -- 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-106) Validation of scm url fails because of ambiquities between source code and site documentation
[ http://jira.codehaus.org/browse/SCM-106?page=comments#action_53258 ] Emmanuel Venisse commented on SCM-106: -- I confirm it's a bug in code. After "scm", we should have ":" or "|". Documentation is correct. What do we need? - a patch for code - a patch for the documentation relative to this bug. > Validation of scm url fails because of ambiquities between source code and > site documentation > - > > Key: SCM-106 > URL: http://jira.codehaus.org/browse/SCM-106 > Project: Maven SCM > Type: Bug > Components: maven-scm-api > Reporter: Dennis Lundberg > > > I am trying out Continuum and am tracking down the cause of why I get an > error regarding the scm url that I provide when adding an ant project. This > has led me here. I copied the scm url from my maven 1 project.xml and got a > very breif error message telling me to enter a valid scm url. > My scm url looks like this: > scm|cvs|pserver|[EMAIL PROTECTED]|C:/Program/cvsnt/repositories|project-name > This works just fine using maven 1. > These two files are involved in this: > maven-scm-api/src/main/java/org/apache/maven/scm/manager/AbstractScmManager.java > maven-scm-site/src/site/apt/cvs.apt > AbstractScmManager.java has the following error message declared: > private final static String ILLEGAL_SCM_URL = "The scm url must be on the > form " > + "'scm: provider>' " > + "where can be > either ':' or '|'."; > which explains how a correct scm url should look. > cvs.apt on the other hand does not have this explanation. It does say: > For all URLs below, we use a colon (:) as separator. If you use a colon for > one of the variables (e.g. a windows path), then use a pipe (|) as separator. > Then follows a bunch of examples, none of which use pipe (|) as a separator. > So to conclude: Continuum uses validateScmRepository(String scmUrl) and maven > scm flags my scm url as invalid, but the docs for the urls are not really > clear about what a delimiter/separator is and where they are in the scm url. > Asuming that the source code is correct, the the docs need updating to > reflect this. There should also be an example using pipe as a separator. If > someone can confirm this I can write a patch for the docs. -- 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-107) [patch] additional info for specifying the clearcase viewstore
[ http://jira.codehaus.org/browse/SCM-107?page=all ] Emmanuel Venisse closed SCM-107: Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 Applied. > [patch] additional info for specifying the clearcase viewstore > -- > > Key: SCM-107 > URL: http://jira.codehaus.org/browse/SCM-107 > Project: Maven SCM > Type: Improvement > Components: maven-scm-provider-clearcase > Reporter: Wim Deblauwe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-2 > Attachments: clearcase-settings.patch > > > This patch updates the clearcase page on the scm website with info on > specifying the viewstore name. -- 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-95) [patch] Update for the maven-scm-site
[ http://jira.codehaus.org/browse/SCM-95?page=all ] Emmanuel Venisse closed SCM-95: --- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-2 Applied. > [patch] Update for the maven-scm-site > - > > Key: SCM-95 > URL: http://jira.codehaus.org/browse/SCM-95 > Project: Maven SCM > Type: Improvement > Reporter: Wim Deblauwe > Assignee: Emmanuel Venisse > Fix For: 1.0-beta-2 > Attachments: site.patch > > > This is a patch for an update to the maven-scm-site. This is an initial try > and it would be nice if the people that implemented the providers would check > to see if all info is correct for their provider. And also if some additional > info is required, then add it like in ClearCase. > I also noted that nobody is in the list of contributers. Maybe you can add > Dan, Mike and me as contributers? > regards, > Wim -- 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
