Hi, On Feb 2, 2008 5:42 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: > > i'd like to copy james-jcr into trunk and add some example > > configurations. development can continue in the sandbox (or not) and > > merged in later (if necessary).
You'll likely need to make some adjustments to the james-jcr build setup that dates back to last summer. Let me know if you need any assistance. > +1 > And I would prefer if development will continue in trunk. Agreed, I'd rather avoid branching the code. I'd be happy to continue working on the JCR component in trunk, though I should point out that I was originally granted commit karma on the premise that I'd work on a sandbox component. Technically I was given write access to all of James, but before taking advantage of that I'd like to make sure that everyone is OK with me working in trunk. > If it does not require big changes to other modules then we don't > need a sandbox or a branch. If instead further development will > require experimental changes to core api then a sandbox or > a branch will be more appropriate. I can foresee some such changes (MIME4J-16 is a good example), but if in any way possible I'd rather break such changes into small reversible steps and explicitly handle backwards compatibility issues where needed than branch any of the core APIs. BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
