On Sat, 2005-05-14 at 13:56 -0400, Tim Reilly wrote: > [Mike Esler wrote:] > > 3 options: (1) decide on reserved vs. unreserved and stick with it, (2) > > create separate commands, or (3) add a boolean to the existing checkout > > command. > > > > I'd like to see it matching (JSR147) javax.wvcm closely which would indicate > (3) above I think: > > - From the spec download: > class ControllableResource:: > void doCheckout(boolean forkOK, List activityList, boolean newActivity, > boolean unreserved) > Checkout this ControllableResource so that its content can be > modified.
I don't think there's any reason we can create a JSR147 layer upon Maven SCM but we don't want to bind to the JSR directly just in case it doesn't mesh with other APIs we might want to support. We'd like to try and make the API powerful enough that we can support layered APIs like JSR147. We would like to model ourselves in much the same way the OJB folks have done it where they have a powerful persistence API and then have built an ODMG, OQL and JDO layer upon it. > Thanks, > -TR > > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org you are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
