The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
GroupId | ArtifactId | Version | Classifier | Type | Optional |
---|---|---|---|---|---|
com.lowagie | itext | 2.1.7 | - | jar | |
com.sleepycat | je | 6.4.25 | - | jar | |
net.sourceforge.nekohtml | nekohtml | 1.9.21 | - | jar | |
org.incava | java-diff | 1.1 | - | jar | |
org.mapdb | mapdb | 0.9.7 | - | jar |
The following is a list of transitive dependencies for this project. Transitive dependencies are the dependencies of the project dependencies.
The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
GroupId | ArtifactId | Version | Classifier | Type | Optional |
---|---|---|---|---|---|
bouncycastle | bcmail-jdk14 | 138 | - | jar | |
bouncycastle | bcprov-jdk14 | 138 | - | jar | |
org.bouncycastle | bcmail-jdk14 | 1.38 | - | jar | |
org.bouncycastle | bcprov-jdk14 | 1.38 | - | jar | |
org.bouncycastle | bctsp-jdk14 | 1.38 | - | jar | |
xerces | xercesImpl | 2.10.0 | - | jar | |
xml-apis | xml-apis | 1.4.01 | - | jar |
JUnit is a regression testing framework written by Erich Gamma and Kent Beck. It is used by the developer who implements unit tests in Java.
This is the core API of hamcrest matcher framework to be used by third-party framework providers. This includes the a foundation set of matcher implementations for common operations.
https://github.com/hamcrest/JavaHamcrest/hamcrest-core
MapDB provides concurrent Maps, Sets and Queues backed by disk storage or off-heap memory. It is a fast, scalable and easy to use embedded Java database.
An HTML parser and tag balancer.
http://nekohtml.sourceforge.net/
Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program. The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual. Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema 1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for evaluation. For more information, refer to the XML Schema page. Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML Catalogs v1.1. Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that it does not yet provide an option to enable normalization checking as described in section 2.13 of this specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.
https://xerces.apache.org/xerces2-j/
XML Commons External Components XML APIs
xml-commons provides an Apache-hosted set of DOM, SAX, and JAXP interfaces for use in other xml-based projects. Our hope is that we can standardize on both a common version and packaging scheme for these critical XML standards interfaces to make the lives of both our developers and users easier. The External Components portion of xml-commons contains interfaces that are defined by external standards organizations. For DOM, that's the W3C; for SAX it's David Megginson and sax.sourceforge.net; for JAXP it's Sun.
http://xml.apache.org/commons/components/external/
iText, a Free Java-PDF library
iText, a free Java-PDF library
Legion of the Bouncy Castle Java Cryptography APIs
The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. The package is organised so that it contains a light-weight API suitable for use in any environment (including the newly released J2ME) with the additional infrastructure to conform the algorithms to the JCE framework.
http://www.bouncycastle.org/java.html
Legion of the Bouncy Castle Java Cryptography APIs
The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. The package is organised so that it contains a light-weight API suitable for use in any environment (including the newly released J2ME) with the additional infrastructure to conform the algorithms to the JCE framework.
http://www.bouncycastle.org/java.html
The Bouncy Castle Java API for handling the Time Stamp Protocol (TSP). This jar contains the TSP API for JDK 1.4. The APIs can be used in conjunction with a JCE/JCA provider such as the one provided with the Bouncy Castle Cryptography APIs.
http://www.bouncycastle.org/java.html
Bouncy Castle CMS and S/MIME API
The Bouncy Castle Java CMS and S/MIME APIs for handling the CMS and S/MIME protocols. This jar contains CMS and S/MIME APIs for JDK 1.4. The APIs can be used in conjunction with a JCE/JCA provider such as the one provided with the Bouncy Castle Cryptography APIs. If the S/MIME API is used, the JavaMail API and the Java activation framework will also be needed.
http://www.bouncycastle.org/java.html
The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.4.
http://www.bouncycastle.org/java.html
An implementation of the longest common subsequences algorithm for Java
http://incava.org/projects/java/java-diff/
Berkeley DB Java Edition is a open source, transactional storage solution for Java applications. The Direct Persistence Layer (DPL) API is faster and easier to develop, deploy, and manage than serialized object files or ORM-based Java persistence solutions. The Collections API enhances the standard java.util.collections classes allowing them to be persisted to a local file system and accessed concurrently while protected by ACID transactions. Data is stored by serializing objects and managing class and instance data separately so as not to waste space. Berkeley DB Java Edition is the reliable drop-in solution for complex, fast, and scalable storage. Source for this release is in 'je-6.4.25-sources.jar', the Javadoc is located at 'http://download.oracle.com/berkeley-db/docs/je/6.4.25/'.