Jan Bartel
Jan Bartel
`Bundle[] bundles = PackageAdminServiceTracker.INSTANCE.getFragmentsAndRequiredBundles((Bundle)context.getAttribute(OSGiWebappConstants.JETTY_OSGI_BUNDLE));` refers to the war bundle being deployed, and should return all of its associated fragments and required bundles. In the osgi tests that we regularly run...
I see. The solution is not to add jsp to the Required Bundles: this effectively puts it onto the webapp's classpath, which is incorrect, even in non-osgi jetty. The correct...
@thomasnikolay my thoughts are: > * the purpose of the jetty is not to check duplicate classes. There are better tools like the extra-maven-enforcer https://www.mojohaus.org/extra-enforcer-rules/banDuplicateClasses.html If you are seeing these...
The jetty-maven-plugin since we changed jetty to use the slf4j-api has only 2 ways to define the _jetty logger_ implementation: 1. when running forked: add the desired slf4j impl to...
If you look at jetty's osgi implementation you'll see that we subclass some of the Configuration classes and other supporting classes that jetty uses at startup time to find resources...
The api search results are definitely broken.
@mwgmnn so prior to this change, is it true that the table would not have been found as part of the schema, and so would have been recreated, but outside...
@mwgmnn so IIUC: prior to this PR, if a user had specified a schema name that was different to the default schema for the database, then the table would have...
See also https://jenkins.webtide.net/job/jetty.project/job/jetty-10.0.x/1619/testReport/junit/org.eclipse.jetty.server/StressTest/Parallel_Stage___Build___Test___JDK17___testNonPersistent/