On 22 Wrz, 21:57, Charlie Collins <[EMAIL PROTECTED]> wrote: > The only things I can think of are both sort of ugly. > > 1. Make changes to the BuildClasspathUtil so that we include provided > for the shell. > > 2. Make your dep compile, and then filter it from the resulting webapp > with the webapp excludes stuff. > > If it makes sense to have "provided" as there for gwt:gwt, then we can > just add it to the util, but, does it make sense?
Yes, it does. I can't include my client jar in war because it is used not only by web application but also by same ejb. So I give it a provided scope and inlcude client jar in ear so its accessible by web and ejb module but this couses errors in hosted mode. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" 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/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
