2010/1/6 Ludovic Champenois <Ludovic.Champenois_at_sun.com>
>
>
>
>>
>> (2) If dependency order is not correct, issue more meaningful error
>> message"
>>
> Good luck with that i.e almost impossible to list all possible
> configuration cases that would trigger an issue with a classpath ordering
> scheme.
>
> In this example, the exception throws by the jvm runtime is not clear
> enough because the mentioned jar is a postprocessed jar that is not meant to
> be used at runtime including test-runtime.
>
Unfortunately Maven by default puts scope provided in the test classpath
which is the problem I hit.
I attached a Maven doc section in the issue tracker.
https://glassfish.dev.java.net/issues/show_bug.cgi?id=11388
> Only solution is this thread and the bug filed that will be indexed by
> Google and Bing for people to find when searching for the exception text :-)
>
And hopefully in the manual as well, maybe in a trouble shooting section.
Seems this tripped up quite a few people already
regards
Richard.