Hi,
it definitely is a good idea, and it's worth doing. SCM has become
commonplace, just like databases. I think few people would object to
lowering the barrier of moving to another SCM system and/or being more
isolated from third-party SCM system changes.
Jan Dvorak
Kev Jackson wrote (shortened):
I was wondering if it would make sense to refactor the SCM tasks into
an interface (scm) and have a set of antlibs that implement that
interface in a vendor specific manner. Such that
<scm command="commit">
is handled appropriately by each SCM system in it's own way, whilst at
the same time exposing a common API to simplify this (very common) set
of tasks. I'm thinking it'd be similar to how the <javac> task
simplifies compiling regardless of which compiler you want to use.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
