Thx for the answer. I will follow your suggest On Tue, Sep 9, 2008 at 3:21 PM, Isaac Truett <[EMAIL PROTECTED]> wrote:
> > 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. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
