Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jetty 9 configuration should honor module system knowledge. #9

Open
joakime opened this issue Nov 18, 2013 · 3 comments
Open

Jetty 9 configuration should honor module system knowledge. #9

joakime opened this issue Nov 18, 2013 · 3 comments

Comments

@joakime
Copy link
Contributor

joakime commented Nov 18, 2013

The Jetty 9 module system has intelligence about the buildup of Jetty based on enabled modules or not. This includes XML (with proper execution ordering), properties, and libraries.

Obviously, since you are stuck on maven/gradlew, the last part about libraries is moot.

However, the proper "glue" for Jetty's modules is the XML, either use the LikeJettyXML example or use the XML itself.

Note: the XML is available via maven on the "config" classified artifacts.

@joakime
Copy link
Contributor Author

joakime commented Apr 17, 2014

Jetty 9.2+ has support for directory lists for configuring Jetty now.

@joakime joakime closed this as completed Apr 17, 2014
@joakime
Copy link
Contributor Author

joakime commented Apr 17, 2014

Err. issues screen should have closed, not set the issue into closed state.
/me shakes fist at eclipse

@joakime joakime reopened this Apr 17, 2014
@joakime
Copy link
Contributor Author

joakime commented Feb 17, 2022

@starksm64 this is still an issue in arquillian core with assumptions on how people configure a server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant