This isn't the entire reactor, but the getClasspathElements()
method. The only situation I can think of this breaking is:
* someone trying to pull apart the classpath looking for directories
and doing something special with them (which would be a horrible
abuse of the method's contract)
On 12/12/2008, at 5:47 PM, Jason van Zyl wrote:
Sent from my iPhone
On Dec 12, 2008, at 7:02 AM, Brett Porter wrote:
Hi,
I was looking at applying the patch for this one, but wasn't happy
with it and looked for a better solution, which I'm also not happy
with :)
Basically, in the r
Sent from my iPhone
On Dec 12, 2008, at 7:02 AM, Brett Porter wrote:
Hi,
I was looking at applying the patch for this one, but wasn't happy
with it and looked for a better solution, which I'm also not happy
with :)
Basically, in the reactor target/classes is always used as the
class
Hi,
I was looking at applying the patch for this one, but wasn't happy
with it and looked for a better solution, which I'm also not happy
with :)
Basically, in the reactor target/classes is always used as the
classpath for projects referring to dependencies inside the reactor
because of
