Ok, that's what I thought you guys would say, but it's gonna be a pain to do. Or maybe not, we'll see. The thing is, the @requiresDependencyResolution annotation can only be one or the other, and then the mojo only has access to whichever is set, then when we pass to our buildClassPath util we will have to re-resolve for the GWT mojo. I am sure it can be done, but it might involve some hoops.
Right now, for the record, 2.0-beta23 has RUNTIME, and 2.0-beta24 has COMPILE. I will add this to the tracker though, and try to hit it next. On Oct 3, 4:59 am, "Mirko Nasato" <[EMAIL PROTECTED]> wrote: > 2008/10/3 Charlie Collins <[EMAIL PROTECTED]> > > > > > And, they aren't. Compile gives us compile and provided in the shell, > > but NOT runtime. What do we really need there though, that is the > > question. Is that really "runtime" AND "compile" - is it special, > > like other GWTisms? > > Uhm maybe yes, because the shell is running the app deployed in a server - > so "runtime" deps should be available - but it's also doing automatic > recompilation - so it needs "compile" ones too. > > Cheers > > Mirko --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
