Download JAR files tagged by project with all dependencies

This project contains utilities for managing components. ECM is what we call an "avalon container", though it is somewhat different in architecture to newer developments like Phoenix and Fortress. Our intend is to someday completely replace ECM with Fortress. In particular, this package contains the ExcaliburComponentManager, usually abbreviated to ECM.

<p> This project offers Exceptions to be used in Java programs. Although their names sound silly, the exceptions themselves are quite usefull. </p> <p> Please refer to the <a href='/exceptions_overview.html'>exceptions overview</a> page for a summary of all available exceptions. </p>

This is a wrapper project for the web-fragment.xml file that sets productionMode=true. When this jar is added to the classpath of a web application, it will run in production mode automatically. This is better used in conjunction with the compilation and minification of resources for production deployment. See the documentation about ES5 compilation and resource minification at https://vaadin.com/docs/v10/flow/web-components/tutorial-webcomponents-es5.html for more information.

A bundle project producing JAX-RS RI bundles. The primary artifact is an "all-in-one" OSGi-fied JAX-RS RI bundle (jaxrs-ri.jar). Attached to that are two compressed JAX-RS RI archives. The first archive (jaxrs-ri.zip) consists of binary RI bits and contains the API jar (under "api" directory), RI libraries (under "lib" directory) as well as all external RI dependencies (under "ext" directory). The secondary archive (jaxrs-ri-src.zip) contains buildable JAX-RS RI source bundle and contains the API jar (under "api" directory), RI sources (under "src" directory) as well as all external RI dependencies (under "ext" directory). The second archive also contains "build.xml" ANT script that builds the RI sources. To build the JAX-RS RI simply unzip the archive, cd to the created jaxrs-ri directory and invoke "ant" from the command line.

dependency-check-core is the engine and reporting tool used to identify and report if there are any known, publicly disclosed vulnerabilities in the scanned project's dependencies. The engine extracts meta-data from the dependencies and uses this to do fuzzy key-word matching against the Common Platfrom Enumeration (CPE), if any CPE identifiers are found the associated Common Vulnerability and Exposure (CVE) entries are added to the generated report.