On Wed, Nov 25, 2009 at 2:25 PM, henrib <hen...@apache.org> 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.
>
> 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 ?
You need two "gump" projects - 1 for JEXL-1 that points to the 1.x branch
http://svn.apache.org/viewvc/commons/proper/jexl/branches/1.x/
....and the other for JEXL-2 which points to trunk.
Until theres a release of JEXL-2 then I doubt any projects will want
to move to the new API/package names. But once it has been released
then the gump descriptors for the dependant projects can be moved from
JEXL-1 to JEXL-2 as and when they upgrade to the use the new package
names.
Niall
> Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
