Details
Description
I've a project which doesn't follow the usual normal maven layout - mostly due to it being based on GWT which requires currently a custom build step to create the WAR and put all the right generated stuff inside. so to make the WAR I need to use the maven assembly plugin; which means I can't really use 'mvn jetty:run' but I can use 'mvn jetty:run-war'.
However I keep forgetting that for this one project I can only run 'mvn jetty:run-war' and that 'mvn jetty:run' won't work for this particular project ![]()
I wonder if it'd be possible to configure a default goal or something so if someone does 'mvn jetty:run' it knows that 'run-war' is the option to really use? Or have some other mechanism of a default 'run goal' which by default is jetty:run but which for GWT style builds you'd set it to be 'mvn jetty:run-war' as the actual target?
Its not a huge biggie - I just keep banging my head on this frequently on different builds and figure it could make the excellent mvn plugin for jetty even nicer to use ![]()
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jesse McConnell [ jesse ] |
| Assignee | Jesse McConnell [ jesse ] | Joakim Erdfelt [ joakime ] |
| Assignee | Joakim Erdfelt [ joakime ] | Jan Bartel [ janb ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 7.5.2 [ 17835 ] | |
| Resolution | Fixed [ 1 ] |