On Tue, 2006-04-11 at 14:57, Zsolt wrote: > I gladly add new functionality or providers to the API but I would be > definitely not the right person to make such modifications in the core API.
Oh, I think you do after all the time you've spend looking into the core by now :) I promise that if you look into the core, find any isses and create a patch I will take a look into the patches and apply them if they're good. > Can somebody make some suggestions? I really have to make a decision: > maven-scm or not. It's up to you to select Maven SCM or not, but I agree with the arguments that Emmanuel had. > Our internal API supports cvs, svn, vss, pvcs and cm-synergy but maven-scm > has much more functionally thus I would love to replace our API but I need a > solution that can be used in a environment with lot of parallel users. It is definitely possible to get that going with Maven SCM, at least it would be easier to add that feature to Maven SCM that to re-implement Maven in your code. Remember that you can always start using Maven SCM's API and then later change (or even re-implement) the providers. You are under no obligation to give the code back (although we would love it! See also Emmanuel's answer) -- Trygve
