If eventually we want Maven/Reactor to be able to Continuously Integrate, we would like to check if the remote SCM repo has been modified and trigger the build. Maybe there is a better way?
================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com > -----Original Message----- > From: Weber, Lance [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 17, 2002 12:14 PM > To: 'Turbine Maven Developers List' > Subject: RE: Diving into the project: VSS Integration > > > Thanks for the pointer, I just took a quick look at the > source. I'm not sure > the abstract SCM interface should specifically assume/support > a differential > check-out, although it could certainly be supported by instances using > properties/parameters, etc. > > > -----Original Message----- > From: Brekke, Jeff [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 17, 2002 11:08 AM > To: 'Turbine Maven Developers List' > Subject: RE: Diving into the project: VSS Integration > > > FWIW Cruise control has some of the abstraction already. > Their interface > really only worries about checking for modifications though... > > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/cruisecontrol/c > ruisecontrol/m > ain/src/net/sourceforge/cruisecontrol/SourceControl.java > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/cruisecontrol/c > ruisecontrol/m > ain/src/net/sourceforge/cruisecontrol/sourcecontrols/ > > I don't believe they have a factory, the scm is specified in > a configuration > file ( xml ). > > ================================================================= > Jeffrey D. Brekke Quad/Graphics > [EMAIL PROTECTED] http://www.qg.com > > > > -----Original Message----- > > From: Weber, Lance [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, September 17, 2002 11:57 AM > > To: 'Turbine Maven Developers List' > > Subject: RE: Diving into the project: VSS Integration > > > > > > I'm sold on the scm abstraction need. Just look at Ant for an > > example of > > what you end up with in the absence of one - I just counted > > eight different > > SCM tasks, each with it's own interface. Ugh. (No offense to > > the super-duper > > Ant project btw). > > > > Okay, off the top of my head, I'd propose starting with an abstract > > SourceCodeManagerFactory that delivers instances of a > > SourceCodeManager > > interface. SourceCodeManager should expose some basic > > consumer operations: > > > > Primary Functions > > ------------------ > > void checkout(CheckoutParms) > > void checkin(CheckinParms) > > void label/tag(name) > > String? getChangelog() > > String? getDiff() > > > > I know there are a lot of secondary and tertiary scm > > operations, but does > > this cover the primary ones to start with? Note, I > > deliberately left out > > initialization, connection, project settings, I'll get to > > those next... > > > > > > -----Original Message----- > > From: James Strachan [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, September 17, 2002 10:28 AM > > To: Turbine Maven Developers List > > Subject: Re: Diving into the project: VSS Integration > > > > > > > > From: "Weber, Lance" <[EMAIL PROTECTED]> > > > Hey folks, I stumbled across references to Maven in James > Strachan's > > > blog... > > > > Me and my big mouth :-) > > > > > this project looks great, exactly what I've been wanting > for awhile > > > now! (and have been too lazy to build on my own ;) > > > > > > In the spirit of wanting to jump in and help contribute I > > thought maybe > > I'd > > > start by trying to incorporate VSS support into either the > > core or as a > > > plug-in (It's one of those corporate standards thang, yeah > > I'd rather be > > on > > > subversion ;). I went through the code and xml/jelly > > scripts yesterday to > > > get the lay of the land and to figure out where to start. > > I'm a little > > > concerned that there seem to be some hard coded cvs > > specific calls in the > > > core and maybe I'm setting myself up for some heartache > by pushing a > > feature > > > in that the architecture isn't ready for...any feedback on this? > > > > At some point real soon it'd be really groovy if we could > get a source > > control abstraction together. It'd probably make a great > > jakarta commons > > project, abstracting away all the grim and gory details of > > the gazillion of > > different source control systems out into a simple API that can be > > implemented on top of various implementations, CVS, subversion, VSS, > > Perforce, ClearCase etc. > > > > There's a bunch of stuff in the Ant project that could be a > > useful start to > > this effort. Also a collegue of Paul Hammant (sorry, > > forgotten the name, I'm > > terrible with names) was discussing the API in IDEA being > pretty neat. > > > > We really need this ASAP. Though probably Jakarta Commons is > > the place to > > work on it, then Maven can reuse whatever ends up there. (On > > a related note, > > the commons-vfs (Virtual File System) is already in Jakarta > > Commons, maybe > > that can be reused somehow?) > > > > > > > Also, any > > > tips, pointers, suggestions would be more than welcome... > > > > I'd surf the maven site and see what you think, then post any > > questions > > here, in IRC or on the turbine-maven-user site. > > > > James > > ------- > > http://radio.weblogs.com/0112098/ > > > > __________________________________________________ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > > > -- > > 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]> > > > > -- > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
