Download JAR files tagged by resolved with all dependencies

Provides goals to discover various paths based on the projects currently building. For example, directory of the execution root project, directory of a given project (based on groupId/artifactId), and highest project basedir that hasn't been resolved from the repository.

This Maven plugin creates in the initialization phase a copy of the original pom where all properties get resolved by its actual values. This substituted POM is used in the further processing. Especially it will be used when an upload to the local or remote repository takes place.

An utility library for ckpackager-maven-plugin. The library is compiled from JavaScript sources checked out from ckeditor.com SVN. A separate module is needed because of eclipse classpath issue. Once it's resolved this module will be folded into ckpackager-maven-module.

The dependency-versions-check plugin verifies that all resolved versions of artifacts are at least the versions specified by the project dependencies. The Maven dependency resolution process will substitute versions for the different artifacts in a dependency tree and sometimes chooses incompatible versions which leads to difficult to detect problems. This plugin resolves all dependencies and collects any requested version. It evaluates whether the resolved versions are compatible to the requested versions and reports possible conflicts.

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.