Download JAR files tagged by ignored with all dependencies

This feature enables support for HTTP Servlets written to the Java Servlet 3.0 specification. The servlets can be packaged in Java EE specified WAR or EAR files. If servlet security is required, an appSecurity feature should also be configured; in the absence of a security feature any security constraints for the application will be ignored.

Toolset for easily comparing JSON structures which may vary in expected ways, such as arrays of content for which order may change, or fields in objects that can be ignored, or matched via patterns. Intended to assist in the validation of JSON-formatted results returned from services.

This module collects all required Iceberg modules and their dependencies, and shades them. Consuming modules only need to mark this module as their dependency to get any required Iceberg libs. This module has no sources of its own, only the built jar file contains the gathered and shaded libs. For Intellij this module is recommended to be ignored, to avoid the dependent modules considering this as a module dependency, they should see this as a library dependency instead.

The maven-dependency-versions-check-plugin is a Maven plugin that verifies that the resolved versions of dependencies are at least the versions specified by the dependencies (or their dependencies etc.) if not higher. More specifically, it will check that * The resolved version of every dependency declared explicitly in the current POM is the same or a newer one than what was stated. If the resolved version has a higher major version number than the declared version, then the plugin will issue a warning if configured to do so. Note that enforced declared versions are ignored by the plugin. * For every explicitly declared dependency in the current POM, all its dependency versions are met. I.e. the resolved versions for all dependencies in that dependency's POM are the same or higher than the one stated in that dependency's POM. This is basically the same check as the one above, but using the dependency's POM! Also, if the current POM has exclusions specified for the dependency, then these transitive dependencies are ignored when checking this particular dependency.