On Tuesday, May 9, 2017 at 1:45:00 PM UTC+2, Frederik Van Hoyweghen wrote: > > I tried both the command line (mvn gwt:compile) and via the IntelliJ Maven > plugin. > Indeed, binding the execution to the prepare-package phase and running *mvn > gwt:compile@compile-common *works, and I'm glad it does. > > If I'm reading what you're saying correctly, this means that there is no > way to invoke all the plugin executions with a simple command? > I personally expected *mvn gwt:compile* to invoke everything it needs (so > everything that comes earlier in it's lifecycle, including the executions I > bound to the prepare-package phase), > or am I missing something obvious? >
"mvn package" (or "mvn prepare-package" if you want, but refer to my second rule of thumb) See https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html (in this case specifically the "a build phase is made up of plugin goals" section) If you'd prefer working with a graph of tasks (like you do in Ant), then again have a look at Gradle. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
