I just finished a first read of the JSR and it looks very promising as a comprehensive long term solution to abstract version control/scm. I guess my only question is one of timing, it looks like any deliverables might be quite a ways out on the horizon (6 months+? Need feedback here).
I think what we're really talking about for a commons project is implementing a set of interfaces that can be deployed quickly, be readily integrated by third parties into any scm system of choice, as well as incorporated into Maven (and any other candidate projects) to solve our immediate scm integration needs. I guess I need a sense of what the community thinks the short vs. long term direction should be. -----Original Message----- From: Christopher Lenz [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 17, 2002 4:28 PM To: Jakarta Commons Developers List Subject: Re: [Proposal] Scamp: Source Control Abstraction Hi Lance, I think this JSR is quite related to your proposal: http://www.webdav.org/deltav/wvcm/ Albeit inspired by WebDAV/DeltaV, I believe it is supposed to be generic. Also, AFAIK, it is initiated by an Eclipse team member, so its implementation is heading open-source. Weber, Lance wrote: > Following some interesting discussions on the Maven list, I'd like to > propose starting an SCM abstraction project, tentatively named Scamp. > > Proposed Goal: > Scamp is a Source Control Manager abstraction layer. It provides a standard > interface to SCM systems allowing common source control operations such as > checkin/checkout, labelling/tagging, reading changelogs and diffs. > > Initial design goals: > -- expose a stable SCM interface contract for consuming applications (Maven, > Ant, etc). > -- provide extensible infrastructure for specific SCM implementations. > -- configuration driven implementations > -- file system independent > -- supports multiple projects, multiple/distributed source providers > > Architecture: > My initial thoughts are to utilize a combination of AbstractSCMFactory and a > SourceControlManager interface with concrete implementations of both. We > might possible need some secondary classes representing projects, > connections, and filesystems, but I'm not sure on those yet. > > 0.1 Release Goals/Requirements: > -- First version of SCM Interface, focused on primary/core SCM operations > -- AbstractSCMFactory > -- Stubbed concrete factories for cvs/vss/vfs? > -- exception infrastructure > > Any thoughts, feedback, requirements, design, existing code pointers, etc > very welcome. Potential participants more than welcome!! > > Thanks, Lance -- Christopher Lenz /=/ cmlenz at gmx.de -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> ___________________________________________________________________________ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
