>>>>> "CM" == Conor MacNeill <[EMAIL PROTECTED]> writes:
CM> I remember the path discussion only vaguely as I was pretty busy CM> at the time. Actually I didn't get involved with this discussion either - for the same reasons as you. Most of the stuff of the JUnit task has been done by Thomas - almost all of it to be honest - and I just quickly browsed through his stuff back then. The point of my mail has been that there has already been a discussion about the PATH issue some weeks ago and that a solution - at least a partial one - was on the way. I just wanted to save us all from some duplicate effort. I didn't want to say "this has been done, there will be a solution and that's it". I hope I didn't sound like this - please tell me if I did. That said, let me answer some of your comments - just looked at Tom's code again for the first time in weeks. CM> The PathElement object seems strange to me. It seems to be not so CM> much a real object, as a set of methods to manipulate the CM> surrounding Path object. One effect is that the Path object is CM> not composed of PathElement objects, which I found odd.
