I think it is acceptable to have 2 separate goals (because the war plugin works the way you described and there is no better workaround): 1. works like gwt:gwt before rc1 (I use beta26) 2. works like gwt-maven:gwt in rc1 I feel more natural to name the 1. as "gwt" but I don't care if it is renamed :) (Of course the same is true for the debug goal...)
I'm sure that most users would use the 1. :) Regards: Norbi On ápr. 10, 03:00, "Robert \"kebernet\" Cooper" <[email protected]> wrote: > Actually, I almost never use filtered resources :) > However, this is one of those things that we had no fewer than *10* bug > reports and a number of list complaints about (the proverbial "they" > here). To be honest, the war:war and install goals don't really slow me down > that much (those are "measured in milliseconds/ones of seconds" operations > on most of the code I work with right now. > This is one of the things I loathe about the m2 WAR plugin: it is entirely > package phase. That means not only filtered resources, but overlays and a > bunch of other stuff can't be guaranteed to have been applied until AFTER > the package phase. > > I can't come up with a good solution here that DOESN'T imply one of the > following: > > 1) war:war runs, but we don't copy it to the local repo (Again, if zipping > up your WAR is taking enough time to notice, this isn't much of a savings) > > 2) making a new goal that is the exact same as :gwt (:gwt-packaged?) but > has an install phase attached. > > I can do #2 if that it the consensus of the list, it just seems a little > ugly from a user-education standpoint. > > > > On Thu, Apr 9, 2009 at 5:47 PM, <[email protected]> wrote: > > > Hello, > > > On Thu, Apr 9, 2009 at 5:29 PM, snorbi <[email protected]> wrote: > > > > Besides I think it is semantically incorrect to always perform an > > > install before starting the shell. > > > HEAR, HEAR!!! Yes, thank you! Sheesh. > > > Please, Robert, I realize you want to use filtered resources (Anyone > > else? Is there a ticket requesting this?) but there are real easy > > alternatives for this in Maven, see below. You're making a significant > > portion, I'd wager >90%, of the user base for this plugin do MORE work > > just to get sane behavior. This is *not* the Maven Way (tm). > > > <build> > > <plugins> > > <plugin> > > <artifactId>maven-resources-plugin</artifactId> > > <executions> > > <execution> > > <phase>validate</phase> > > <goals> > > <goal>copy-resources</goal> > > </goals> > > <configuration> > > <outputDirectory>blah/blah</outputDirectory> > > <resources> > > <resource> > > <directory>src/main/resources</directory> > > <filtering>true</filtering> > > </resource> > > </resources> > > </configuration> > > </execution> > > </executions> > > </plugin> > > </plugins> > > </build> > > > -jesse > > > -- > > There are 10 types of people in this world, those > > that can read binary and those that can not. > > -- > :Robert "kebernet" Cooper > ::[email protected] > Alice's cleartext > Charlie is the attacker > Bob signs and > encryptshttp://pgp.mit.edu:11371/pks/lookup?op=get&search=0x9E8759F8 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
