On 25/11/2009, henrib <[email protected]> wrote: > > > One last thing, just to be safe; if I was to perform the serie of 'svn > mv...' on the java files in the trunk, anything that currently depends upon > JEXL's trunk would stop compiling.
Why? So long as the result of the commits was still consistent, I don't see what the problem is. > This would imply the gump/nightly commons builds that happily cope with the > current JEXL trunk will fail forever (probably 47 projects...). Forever? Why? > How can I prevent this from happening? I'm not sure that it will happen. But even if it does, it's not a disaster - Gump/nightly builds will fail from time to time; that's what they are there for. > What's the procedure for this kind of "renaming project package" cases ? Make sure that the commits are self-contained as far as possible. > Should I create a "jexl2/" directory in svn ? Won't that confuse the history somewhat? > Thanks > > > -- > View this message in context: > http://n4.nabble.com/JEXL-2-0-o-a-c-jexl-or-o-a-c-jexl2-tp727081p787578.html > > Sent from the Commons - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
