Yeah, for a third party GWT library, it's *compile* that you want, because you only need that at compile time. After it's compiled that source jar ends up as JavaScript at runtime, so it's not a runtime dep.
Nevertheless, good question, and good to note, not stupid at all . This is actually something we have been having ia debate about here with regard to how to handle the deps for the shell. The GWTShell is "special." It's not really the same as a real "runtime" container, but sometimes it needs dependencies from any of the maven scopes. For example, sometimes stuff that is scoped "provided" may be needed in the shell, if you typically let your contain provide your db connection pooling or something, GWTShell doesn't have that, so it might need provided stuff. Also, there are occasions where it might need runtime stuff (fewer, but still happens). Right now we have the gwt:gwt settings to include everything in "compile" because that also brings in provided, but it skips runtime. We have been planning on just giving the shell access to all of them, but we have to wrestle with Maven to do that (it doesn't like that idea and makes it hard to include compile and runtime together). Long story, but for now yeah, use compile or provided for whatever you want to end up in the shell. On Oct 8, 6:13 am, larshub <[EMAIL PROTECTED]> wrote: > I found the solution. Something stupied :-) > > The dependency must be of scope "compile", "runtime" will not work - > obviously. For a experienced gwt and maven user this is evidently. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
