Short version: betwixt shortcomings. Long Version: - We needed some scm system neutral way to store the 'connection' details in the pom. - allowing arbitrary elements for other scms meant we couldn't do it in betwixt - using a 'jdbc-style' url meant we could easily implement a factory to find Scm Provider Implementations - if we aren't using cvs then you'd need an Scm provider supported by maven. - the format after scm:<scm-name>: is completely up to the scm provider code.
-- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers Jon Scott Stevens <[EMAIL PROTECTED]> 06/02/02 10:17 AM Please respond to "Turbine Maven Developers List" To: Turbine Maven Developers List <[EMAIL PROTECTED]> cc: Subject: Re: cvs commit: jakarta-turbine-maven project.xml on 6/1/02 4:31 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > - > <connection>scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic/jakarta-tur > bine-maven</connection> > + > <connection>scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:jakarta-tur > bine-maven</connection> Why not make these new elements instead of having to parse them? For example, what if the CVS server lives on a different port # than the default on? That would break the parser... What if we aren't using CVS? -jon -- 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]>
