Jetty

maven-jetty-plugin run-exploded and ContextHandlers are not working together

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 8.0.0.M1
  • Fix Version/s: None
  • Component/s: Maven
  • Labels:
    None
  • Environment:
    maven 3
    maven jetty plugin 7.2.2.v20101205
  • Testcase included:
    yes
  • Number of attachments :
    0

Description

I have such a configuration at my maven jetty plugin.

<contextHandlers>
<contextHandler implementation="org.eclipse.jetty.server.handler.ContextHandler">
<contextPath>/images</contextPath>
<resourceBase>D:/LocalProjects/istanbul/html/static</resourceBase>
<handler implementation="org.eclipse.jetty.server.handler.ResourceHandler"/>
</contextHandler>
</contextHandlers>

This configuration is working like a charm with jetty:run command but it is not working with jetty:run-exploded.

Is this expected behaviour?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Michael Gorovoy added a comment -

Greetings,

The maven-jetty-plugin's jetty:run-war and jetty:run-exploded goals were originally meant to be used on a war file, that by definition can only contain a single web application. For this reason, <contextHandlers> configuration element is currently ignored by the above goals.

If you could provide us with a description of your use case, please reopen this ticket, and we will then decide if the support for the feature you are requested could be added.

-Michael

Show
Michael Gorovoy added a comment - Greetings, The maven-jetty-plugin's jetty:run-war and jetty:run-exploded goals were originally meant to be used on a war file, that by definition can only contain a single web application. For this reason, <contextHandlers> configuration element is currently ignored by the above goals. If you could provide us with a description of your use case, please reopen this ticket, and we will then decide if the support for the feature you are requested could be added. -Michael
Hide
Permalink
Torsten Krah added a comment -

Hm the use case is the same as with jetty:run.
I've got e.g. a webapp A which may need another webapp B to run (lets say a solr backend server B and my search webapp A).

I would than configure the pom to run a context handler for the solr backend B and the main webapp would be my search one.
If i need to package things via overlays i must run it via run-exploded to get anything useful - but than the webapp B would not run. Using jetty:run both would start and all would be fine.
Thats what my usecase is - indeed i've got 4 webapps i want to start via context handler (all are war files) and my main webapp should be a "war" too.
The only workaround now is to have a dummy webapp which does run all others via contextHandler stuff ... not what i expect - what do you think about?

Show
Torsten Krah added a comment - Hm the use case is the same as with jetty:run. I've got e.g. a webapp A which may need another webapp B to run (lets say a solr backend server B and my search webapp A). I would than configure the pom to run a context handler for the solr backend B and the main webapp would be my search one. If i need to package things via overlays i must run it via run-exploded to get anything useful - but than the webapp B would not run. Using jetty:run both would start and all would be fine. Thats what my usecase is - indeed i've got 4 webapps i want to start via context handler (all are war files) and my main webapp should be a "war" too. The only workaround now is to have a dummy webapp which does run all others via contextHandler stuff ... not what i expect - what do you think about?
Hide
Permalink
Jan Bartel added a comment -

I think this (and a couple other things) should be able to be configured also for run-war and run-exploded goals.

Show
Jan Bartel added a comment - I think this (and a couple other things) should be able to be configured also for run-war and run-exploded goals.
Hide
Permalink
Jan Bartel added a comment -

You can now use <jettyConfig> and <contextHandlers> elements with run-war and run-exploded goals - it was an oversight that you couldn't before.

Show
Jan Bartel added a comment - You can now use <jettyConfig> and <contextHandlers> elements with run-war and run-exploded goals - it was an oversight that you couldn't before.

People

  • Assignee:
    Jan Bartel
    Reporter:
    Cem Koc
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: