Regardless, simply remove the conflicting jar from whatever classpath is in use by the operation that is failing. If you can't remove the jar entirely due to other dependencies, then change the order that the two conflicting jars appear in your classpath. The one that appears first gets loaded first. Subsequent classpath entries containing the same class are ignored.
On Mon, Sep 8, 2008 at 4:32 PM, massimo malvestio <[EMAIL PROTECTED]> wrote: > Hi thx for response, but jar is not deployed. I try to be clearer; the > problem happens during the phase of global test of all my jsp files. First > of all I compile my webapp, including javascript translation, then I run jsp > tests. The only fact of using a webapp to manage all build process, even if > using ant tasks, generates some problems... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
