On 30 Jul 07, at 6:51 PM 30 Jul 07, Kenney Westerhof wrote:
Hi,
*Phew*, boy, did I open a can of worms when fixing this..
Short: it's fixed.
Nice hunting.
Long:
I broke it... Though I only broke an obscure hack.. This code
shouldn't
have been committed though I understand why it's do
Hi,
*Phew*, boy, did I open a can of worms when fixing this..
Short: it's fixed.
Long:
I broke it... Though I only broke an obscure hack.. This code shouldn't
have been committed though I understand why it's done.
(below jdcasey's comments, there's a long piece I wrote explaining what goes
o
IIRC, path resolution was taking place in the project builder...which
would mean that it could have happened during kenney's cleanup of the
interpolation. Not sure, though. (I'm fairly certain on the timing of
the path translation, though...I'm pretty sure it happened during
project-buildin
I'm trying to find the source of the problem, but it0088 is broken on
trunk and that's the very nasty ${project.build.directory} not
resolving to a full path which caused a tremendous amount of grief
between the 2.0. and 2.0.1 releases.
I can tell immediately what broke it, but if anyone wa
