+1 as long as this doesn't break previous builds
On 5/3/06, Brett Porter <[EMAIL PROTECTED]> wrote:
It seems to be common to hit XML problems with surefire because it is
using child first classloading (like a webapp) to ensure you get what
you ask for which often causes xml problems because the
+1
Emmanuel
Brett Porter a écrit :
It seems to be common to hit XML problems with surefire because it is
using child first classloading (like a webapp) to ensure you get what
you ask for which often causes xml problems because the apis are not in
the same place as the implementation.
I'd li
On 3 May 06, at 11:38 PM 3 May 06, Brett Porter wrote:
It seems to be common to hit XML problems with surefire because it
is using child first classloading (like a webapp) to ensure you get
what you ask for which often causes xml problems because the apis
are not in the same place as the i
Brett Porter wrote on Thursday, May 04, 2006 5:39 AM:
> It seems to be common to hit XML problems with surefire because it is
> using child first classloading (like a webapp) to ensure you get what
> you ask for which often causes xml problems because the apis
> are not in
> the same place as the
On May 3, 2006, at 11:38 PM, Brett Porter wrote:
It seems to be common to hit XML problems with surefire because it
is using child first classloading (like a webapp) to ensure you get
what you ask for which often causes xml problems because the apis
are not in the same place as the implemen
It seems to be common to hit XML problems with surefire because it is
using child first classloading (like a webapp) to ensure you get what
you ask for which often causes xml problems because the apis are not in
the same place as the implementation.
I'd like to suggest we make two changes:
- c
