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.
This would imply the gump/nightly commons builds that happily cope with the current JEXL trunk will fail forever (probably 47 projects...). How can I prevent this from happening? What's the procedure for this kind of "renaming project package" cases ? Should I create a "jexl2/" directory in svn ? 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
