can we configure the plugin so that 'jetty:run' means 'jetty:run-war'

problem with this is that run and run-war are two separate mojo's in the plugin and maven does the selecting, its not really something that can be configured at runtime unless we enable to run plugin to have a little mechanic to execute that other mojo based on some config...

there are a couple of ways you could get around it, but it would override your usage of jetty:run directly, defining a profile that you activated that did the right thing for you and wired the jetty plugin into the lifecycle...but that still messes up the key-finger memory bits :/

we could take a patch on jetty mojo if your interested

if we just had jelly in maven2 it would all be better....

Could we just put something into the configuration in the pom so that if you attempted mvn jetty:run then it would fail with a warning saying that only jetty:run-war works for this webapp.

I've had the same problem with the cometd demos and people thinking they just don't work. of course, if we integrate davids resource collection so that overlays and stuff work, that would be even better..... but a simple warning will do for now.

Geeze, this kinda goes against my grain somewhat, but what about if I added a <goals> configuration element that could contain a coma separated list of goals that work for this webapp?

No matter which goal was invoked, it would check for a <goals> element. If the element doesn't exist, then all goals will work. Otherwise, if the goal that was invoked is not listed in the <goals> element, an error message is printed along with the list of acceptable goals?

Jan

joakim, thoughts?

My thoughts...

We could make the plugin aware of GWT style builds and fail the attempt to use jetty:run in those situations.

As for bridging from jetty:run to jetty:run-war automatically, that wouldn't really help.
As the user specified jetty:run on the command line, maven build has already loaded the plugin metadata, including the phase desired from that metadata, and is executing to that desired phase, which in in the case of jetty:run means that the WAR was built again, but this time in a likely non-GWT mode.
Then the jetty:run mojo executes. At this point, bridging out to jetty:run-war would make no sense, as i would expect the project to no longer be GWTed (if that is even a word).

Let's just go with something that disables jetty:run with a polite warning for now, so we can close this issue.

Fixed by adding a new <excludedGoals> configuration element. To stop eg the "jetty:run" goal being used with the webapp, do:

<configuration>
<excludedGoals>
<excludedGoal>run</excludedGoal>
</excludedGoals>
</configuration>