Issue #6354 - OSGI manifest for slf4j-api packages lower limit should be 1.7
* Fixed OSGi manifest in all jars.
* Make osgi tests work with slf4j < 2.0.0.
This required to remove the dependency on SLF4J from the demos.
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Co-authored-by: Jan Bartel <janb@webtide.com>
* Issue #5798 fix jetty runner startup error and add jsp support as well
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
* Add test to ensure jetty runner starts correctly
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
* remove unused imports
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
* fix help description
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
* improvement based on Joakim comment, add it test with the path
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
Fixed javadoc generation error.
Apparently, this is caused by a doxia dependency of asciidoctor-maven-plugin
that transitively pulls in Apache HttpClient, but at an older version
that causes this error:
Exception in thread “main” java.lang.NoSuchMethodError: ‘org.apache.http.HttpHost org.apache.http.client.utils.URIUtils.extractHost(java.net.URI)’
Adding Apache HttpClient as an explicit dependency of the asciidoctor-maven-plugin
works around the issue.
Co-authored-by: olivier lamy <oliver.lamy@gmail.com>
Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
* New top level /documentation/
Which is a parent pom
* Existing /jetty-documentation/ moved to new
/documentation/jetty-documentation/ location
* New /documentation/jetty-asciidoctor-extensions/ project
Created from the java code in the old
/jetty-documentation/src/main/ tree
* Referencing new jetty-asciidoctor-extensions project
in asciidoc plugin on /documentation/jetty-documentation/pom.xml
* All projects in /documentation/ are now on
org.eclipse.jetty.documentation groupId
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
This brings in a change to the javax.servlet.api module-info
to open the javax.servlet.resources package to all modules,
so that the dtds and xsds can be retrieved as resources, either
from the context Classloader.getResource, or
from the ServletContext.class.getResource.
Signed-off-by: Jan Bartel <janb@webtide.com>
* Remove PMD from build
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
* Attempt to fix log4j2 distribution test
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
* Fixing jetty-start tests to use configured maven.repo.uri property
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
* Using ${env.MAVEN_REPO_URI} configured at Jenkins.
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
* no need of this
Signed-off-by: olivier lamy <oliver.lamy@gmail.com>
Co-authored-by: olivier lamy <oliver.lamy@gmail.com>
* Fixes#5902 - Grab Jetty startup output in documentation.
Implemented an Asciidoctor extension that uses `JettyHomeTester` to run
Jetty and capture its output.
This extension is triggered by the `ServiceLoader` mechanism, so the
documentation jar is now in the plugin classpath.
Introduced `jetty-halt.xml` so that the JVM can be halted.
In this way, Jetty does not produce the "stopping" log lines and
therefore they won't be grabbed and included in the documentation.
Used the new `include::jetty[]` directive in the documentation.
Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
Co-authored-by: Greg Wilkins <gregw@webtide.com>
