[jetty-dev] [jira] (JETTY-1516) Jetty mavn plugin run-forked doesn't respect configuration set using file from contextXml option

Stepan Vavra
commented on JETTY-1516

Jetty mavn plugin run-forked doesn't respect configuration set using file from contextXml option

Jan,

thanks for the work you've done!

I was thinking about the implementation and the different behavior for those two goals. What do you think about leaving the fields in the mojo uninitialized and then initialize the fields in the Starter using the constants which are now in the mojo?

I'm not sure if what I'm saying is really applicable though.

I would really appreciate if there would be at least a workaround how to get rid off those default values from the mojo (especially for the web app resources).

Frankly saying, isn't it better to set Jetty configuration the way how Jetty was designed than to forward several values, from the plugin config, using a temporary file (fork.props)?

Stepan

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email