Download JAR files tagged by versions with all dependencies

Eclipse Gemini Blueprint project makes it easy to build Java applications that run in an OSGi framework. By using Gemini Blueprint, applications benefit from using a better separation of modules, the ability to dynamically add, remove, and update modules in a running system, the ability to deploy multiple versions of a module simultaneously (and have clients automatically bind to the appropriate one), and a dynamic service model.

This maven plugin is responsible to create a Fat JAR bundle containing all the dependencies specified in a POM file. Sometimes users need to unpack specific dependency (eq. zip, tar etc) before packing the dependency as this dependency could contain other jar files. The primary motive is to collect all the dependencies including the plain jar dependencies and the other jar dependencies that reside in other dependency (eq. zip, tar etc). Apart from this, it could also update the versions of the specified dependencies before wrapping in a big fat JAR bundle. This internally uses bnd to wrap all the dependencies in a single fat JAR.

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.

This is a client to access Cloud Bigtable (https://cloud.google.com/bigtable/) via the HBase APIs. There are a handful of modules in this project. The bigtable-hbase-x.x projects are intendned to be the projects which users interact with. The x.x versions in the bigtable-hbase-x.x projects represent the hbase major and minor versions which the project supports. For example, bigtable-hbase-1.0 will integrate with all hbase 1.0.x releases and bigtable-hbase-1.1 will integrate with all hbase 1.1.* releases. The bigtable-protos, bigtable-client-core and bigtable-hbase modules are meant to be used as components of bigtable-hbase-x.x. Those submodules may be usedful outside of the bigtable-hbase-x.x projects, but have not been thoroughly tested in other scenarios.

Maven plugin leveraging the baselining feature of the bnd library[0]. The plugin automatically checks an OSGi bundle's package export versions need to be incremented, in accordance with semantic versioning[1,2]. [0] http://blog.osgi.org/2013/09/baselining-semantic-versioning-made-easy.html [1] http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf [2] http://semver.org/spec/v2.0.0.html

The Woden project is a subproject of the Apache Web Services Project to develop a Java class library for reading, manipulating, creating and writing WSDL documents, initially to support WSDL 2.0 but with the longer term aim of supporting past, present and future versions of WSDL. There are two main deliverables: an API and an implementation. The Woden API consists of a set of Java interfaces. The WSDL 2.0-specific portion of the Woden API conforms to the W3C WSDL 2.0 specification. The implementation will be a high performance implementation directly usable in other Apache projects such as Axis2.