Download JAR files tagged by configuration with all dependencies

This service implements the Indexer and Searcher interface of WebLab and uses a embedded SOLR engine in order to realize the functions. Unlike the other SolR service, this version does not need having SolR installed. Configuration of the SOLR service can be done through IndexerBean.xml and SearcherBean.xml whereas the SolR instance configuration resides in the solr directory.

Spring AMQP is framework that makes it easy to write Java applications for the Advanced Message Queue Protocol. It supports a variety of common high-level messaging patterns, like synchronous and asynchronous consumers, synchronous producers, automatic re-connection, transactions, batching. The emphasis is on declarative configuration and a POJO programming model without hiding the full power of the underlying protocol.

This project produces the Mojo that can build a proper release.xml for the SQuirreLSQL update site, given a directory where the updated jar artifacts are located. This plugin accepts a directory in it's configuration and expects to find three sub-directories there : core, plugins and i18n. It then categorizes the artifacts found in those directories accordingly in the final release.xml file, that is generated in the specified folder.

This maven plugin extends the maven dependency plugin's CopyDependenciesMojo to provide more precise control over which artifacts are included in the copy operation. Specifically, in addition to the normal configuration provided by the CopyDependenciesMojo, it accepts a configuration of includedArtifacts which is a list containing a single entry for each includedArtifact where the value is the groupId and the artifactId joined by a colon (":")

This library provides UTF-7 and Modified UTF-7 Charsets for Java. Sun's default Java distribution lacks support for the UTF-7 character set. Though it is not used commonly, it is still sometimes encountered in e-mails, or applications handling e-mail. The package is written as java.nio.charset extension, which means it can be used without special installation or configuration. Just drop the jar in your classpath, and you are ready to go.

The Glassfish Maven Plugin is a Maven2 plugin allowing management of Glassfish domains and component deployments from within the Maven build lifecycle. It encapsulates domain configuration and deployment attributes within the build configuration for a more rapid development integration loop and simplified management of continuous integration testing of components destined for deployment within the Glassfish V2 and later JavaEE containers.

An SLF4J log provider that directly implements the SLF4J API and provides logging output suitable for console output (i.e. not to a file). The width of the output is restricted to the terminal width, with the possibility to split the width into multiple sections, each which may be a fixed width, or 'auto' which divides all remaining space amongst other automative sections. Any log attribute fields may then be placed in any of the sections with a particular alignment. Text will not overflow out of its section. Sections may be colour or styled with other text attributes, including hyperlinks for supported termins. Emoticons and other graphical sequences may be used in place of log levels. Configuration is achieved via 'ini' type files, which are reload automatically when changed.

Each Java project should follow a given coding style. I.e., all contributions to the source code should use the same formatting rules, design principles, code patterns, idioms, etc. I published such a coding style in my GitHub project codingstyle (https://github.com/uhafner/codingstyle) - I am using this coding style in my lectures about software development at Munich University of Applied Sciences and in all of my open source projects. If you want to use this coding style as well, you can use this Maven POM as parent of your own POM. Then you get the configuration several static analysis and testing tools for free.

A secure, REST administrative connector that can be used locally or remotely using any Java developer kit. This connector enables remote access from a Java client or directly through an HTTPS call. The administrator and reader roles protect the connector. The connector requires TLS to keep the communication confidential. The HTTPS port used by the connector is defined through the default HTTP endpoint. This feature supersedes the restConnector-1.0 feature. It enables the REST handler configuration APIs. When this feature is combined with features supporting configuration validation, the corresponding REST handler validation APIs are enabled.