search

saiddfhi / gwt-maven

Automatically exported from code.google.com/p/gwt-maven
0 stars 0 forks source link

Tweak the default executions #145

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Make sure the default executions include

compile
gwt
test

or such (maybe not mergewebxml, i18n or gen by default?)

note that if people tweak the executions on their own they override the
defaults, but at least check the defaults and make sure they make sense

Original issue reported on code.google.com by charlie....@gmail.com on 10 Sep 2008 at 12:55

GoogleCodeExporter commented 9 years ago 
After reading some more Maven documentation, for example
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
I think it's not possible to just add a plugin to the build section and expect 
it to
automatically bind its goals to the build lifecycle. Although you can specify a
default phase in the corresponding mojo (what you have done correctly), you 
have to
list the goal in the executions section explicitly to "activate" this binding.
That's how I understand it now...

Original comment by holger.b...@googlemail.com on 14 Sep 2008 at 4:01

GoogleCodeExporter commented 9 years ago 
Yeah I have been reading that, and more, and it seems we would have to have our 
own
packaging type to control it any further, I am not sure it's worth doing that 
at this
time (more configuration in one area, less in another, and a bit more 
abstract). 

Closing and not addressing for now.

Original comment by charlie....@gmail.com on 14 Sep 2008 at 6:53