It is a "compile" dependency, in that it is required for (gwt) compiling, except it doesn't need to be packaged into the webapp, so option 2. would be good if it works. But I'm not sure you can apply war plugin exclusions to jar dependencies, I suspect you can only exclude resources. Anyway I'll come back to this at some later point.
2008/9/22 Charlie Collins <[EMAIL PROTECTED]> > > 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? > > On Sep 22, 6:57 am, "Mirko Nasato" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm hitting an annoying issue with dependencies. I'm using a single > widget > > from gwt-incubator[1]. Since the gwt-incubator.jar is 1.6M and it's only > > required by gwt:compile to generate JavaScript code, I don't want it > > packaged into my webapp. So I set its dependency to > > <scope>provided</scope>, like for gwt-user. > > > > Now the problem is that this works fine for gwt:compile, but not for > > gwt:gwt: the shell starts up but can't find the inherited module.gwt.xml. > > This sort of makes sense given the meaning of 'provided' in Maven, but > GWT > > as usual is a bit special. Any idea if there's a way around this? > > > > Thanks > > > > Mirko > > > > [1]http://code.google.com/p/google-web-toolkit-incubator/ > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
