Default provider [files] section always executed #6049
Assignees
Labels
Comments
sbordet
added a commit
that referenced
this issue
Mar 9, 2021
Keeping only enabled modules when processing the modules, so that default provider modules don't get processed. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 8, 2021
Keeping only enabled modules when processing the modules, so that default provider modules don't get processed. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 8, 2021
Updates after review. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 11, 2021
Updates after review. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 12, 2021
* Fixes #6049 - Default provider [files] section always executed Keeping only enabled modules when processing the modules, so that default provider modules don't get processed. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version
10.0.x
Description
java -jar start.jar --add-modules=http,logging-logbackcopiesresources/jetty-logging.properties, but it should not.Interestingly,
java -jar start.jar --add-modules=logging-logback,httpdoes not copyresources/jetty-logging.properties.Since an explicit provider has been configured, the default provider should be out of the picture.
The text was updated successfully, but these errors were encountered: