I agree. We cannot upgrade to rc1 from beta26 because of these changes :[, although I miss the compileSkip flag very much from beta26.
Besides I think it is semantically incorrect to always perform an install before starting the shell. What happens if I definitely do not want to install the artifact? (Eg. because it has serious bugs, and I only want to start the shell to find these bugs.) Installation should happen only when the artifact is ready to be shared via the local repo, it should never be implicit! Regards: Norbi On ápr. 9, 22:36, Farrukh Najmi <[email protected]> wrote: > On Wed, Apr 8, 2009 at 7:58 PM, Robert "kebernet" Cooper <[email protected] > > > wrote: > > Yes, they changed to a lifecycle phase in order to facilitate people who > > want to use filtered resources when they are working with it. > > This is a real step backward as it impacts our collective productivity > rather seriously. Waiting for install target is too long (even with > compile/test skips) when one just want to make a server side change and > restart the shell. IMHO "people who want to use filtered resources" is less > common and there should be a separate goal for that. > > BTW, I am not clear who "they" is that made the change. > > > > > The shorthand version is you can do -Dmaven.test.skip > > -Dgoogle.webtoolkit.compileSkip -Dgoogle.webtoolkit.testSkip to bypass the > > stuff you usually want to bypass and get to the shell now. (This is how I > > have been working) > > Thanks for the tip. Its an improvement but its still not good to have to > build and install the war. > > -- > Regards, > Farrukh --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
