ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib and ISC and FTL and RSA-MD
ASL 1.1 and ASL 2.0 and BSD and BSD with advertising and GPL+ and GPLv2 and GPLv2 with exceptions and IJG and LGPLv2+ and MIT and MPLv2.0 and Public Domain and W3C and zlib
ASL 1.1 and ASL 2.0 and xpp and BSD and Public Domain
acquired package info from repodata DB: repodata/f1f85c23079e7764ad00378a9fc5d660b89a03657290e75426caf7be5b7da462-primary.sqlite.bz2
Provides utility methods for creating JARs and other archive files from a Maven project.
Source Plugin creating a jar archive of source
The Source Plugin creates a jar archive of the source files of the current project. The jar file is, by default, created in the project's target directory.
The OpenJDK runtime environment 11 without audio and video support.
XML parser optimized for round-tripping and code reuse
XML parser optimized for round-tripping and code reuse with main features being: * Allows 100% round-tripping, even for weird whitespace between attributes in the start tag or in the end tag * Suitable for building editors and filters which want/need to preserve the original file layout as much as possible * Error messages have line and column information * Easy to reuse individual components * XML 1.1 compatible
Plugins and extensions for building Eclipse plugins and OSGI bundles with Maven
Tycho is a set of Maven plugins and extensions for building Eclipse plugins and OSGI bundles with Maven. Eclipse plugins and OSGI bundles have their own metadata for expressing dependencies, source folder locations, etc. that are normally found in a Maven POM. Tycho uses native metadata for Eclipse plugins and OSGi bundles and uses the POM to configure and drive the build. Tycho supports bundles, fragments, features, update site projects and RCP applications. Tycho also knows how to run JUnit test plugins using OSGi runtime and there is also support for sharing build results using Maven artifact repositories. Tycho plugins introduce new packaging types and the corresponding lifecycle bindings that allow Maven to use OSGi and Eclipse metadata during a Maven build. OSGi rules are used to resolve project dependencies and package visibility restrictions are honored by the OSGi-aware JDT-based compiler plugin. Tycho will use OSGi metadata and OSGi rules to calculate project dependencies dynamically and injects them into the Maven project model at build time. Tycho supports all attributes supported by the Eclipse OSGi resolver (Require-Bundle, Import-Package, Eclipse-GenericRequire, etc). Tycho will use proper classpath access rules during compilation. Tycho supports all project types supported by PDE and will use PDE/JDT project metadata where possible. One important design goal in Tycho is to make sure there is no duplication of metadata between POM and OSGi metadata.
Support macros and scripts for maven packaging
The maven-local package contains macros and scripts to support packaging Maven artifacts.
Core part of Apache Maven that can be used as a library.
A library to reliably execute external processes from within the JVM
The apache-commons-exec package contains a library to reliably execute external processes from within the JVM.
This package provides mechanisms to manage tests on Mojo.
A collection of various utility classes to ease working with strings, files, command lines, XML and more.
A set of basic GNU tools commonly used in shell scripts
These are the GNU core utilities. This package is the combination of the old GNU fileutils, sh-utils, and textutils packages.
Java API for working with compressed files and archivers
The Apache Commons Compress library defines an API for working with ar, cpio, Unix dump, tar, zip, gzip, XZ, Pack200 and bzip2 files. In version 1.14 read-only support for Brotli decompression has been added, but it has been removed from this package.
Provides a test harness for Maven integration tests.
The Eclipse Platform is the base of all IDE plugins. This does not include the Java Development Tools or the Plugin Development Environment.
Bash is the GNU Project's shell. Bash is the Bourne Again SHell. Bash is an sh-compatible shell that incorporates useful features from the Korn shell (ksh) and C shell (csh). It is intended to conform to the IEEE POSIX P1003.2/ISO 9945.2 Shell and Tools standard. It offers functional improvements over sh for both programming and interactive use. In addition, most sh scripts can be run by Bash without modification.
The javapackages-filesystem package contains some basic directories into which Java packages install their content.
Java bytecode manipulation and analysis framework
ASM is an all purpose Java bytecode manipulation and analysis framework. It can be used to modify existing classes or dynamically generate classes, directly in binary form. Provided common transformations and analysis algorithms allow to easily assemble custom complex transformations and code analysis tools.
XMvn Core module implements the essential functionality of XMvn such as resolution of artifacts from system repository. XMvn core is needed by all other modules.
This package provides minimal version of XMvn, but can't use remote repositories.
The Clean Plugin is used when you want to remove files generated at build-time in a project's directory.
Components to manipulate compilers for Plexus
Plexus Compiler is a Plexus component to use different compilers through a uniform API.
ECJ is the the Eclipse Compiler for Java. It is also known as the JDT Core batch compiler.
The OpenJDK runtime environment 8 without audio and video support.
A Java package for unit testing frameworks
JUnit is a simple framework to write repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.
This test framework project for surefire.
Library of matcher objects for building test expressions
Provides a library of matcher objects (also known as constraints or predicates) allowing 'match' rules to be defined declaratively, to be used in other frameworks. Typical scenarios include testing frameworks, mocking libraries and UI validation rules.
The Plexus project provides a full software stack for creating and executing software projects. It provides a number of pre-built components for common tasks and toolkits such as Jetty, Velocity, Hibernate, i18n, and many more. However, Plexus is also able to reuse your existing components written for other IoC frameworks such as Spring, Avalon and Pico Container unmodified, as well as allowing you to reuse your existing code inside the Plexus Container. Plexus comes with an application server that can run your applications, making it trivial to build a standalone executable distribution with common features such as service execution if needed. However, Plexus applications can be run in any environment by embedding the container in an existing application, including Java EE applications or web applications.
Tasty mocking framework for unit tests in Java
Mockito is a mocking framework that tastes really good. It lets you write beautiful tests with clean & simple API. Mockito doesn't give you hangover because the tests are very readable and they produce clean verification errors.
This module contains public interface for functionality implemented by XMvn Core.
plexus-component-annotations provides the Java 5 annotations for plexus components.
The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks (e.g. java.util.logging, logback, log4j) allowing the end user to plug in the desired logging framework at deployment time.Before you start using SLF4J, we highly recommend that you read the two-page SLF4J user manual. Note that SLF4J-enabling your library implies the addition of only a single mandatory dependency, namely slf4j-api.jar. If no binding is found on the class path, then SLF4J will default to a no-operation implementation. In case you wish to migrate your Java source files to SLF4J, consider our migrator tool which can migrate your project to use the SLF4J API in just a few minutes. In case an externally-maintained component you depend on uses a logging API other than SLF4J, such as commons logging, log4j or java.util.logging, have a look at SLF4J's binary-support for legacy APIs.
The standard Java libraries fail to provide enough methods for manipulation of its core classes. The Commons Lang Component provides these extra methods. Lang provides a host of helper utilities for the java.lang API, notably String manipulation methods, basic numerical methods, object reflection, concurrency, creation and serialization and System properties. Additionally it contains basic enhancements to java.util.Date and a series of utilities dedicated to help with building methods, such as hashCode, toString and equals. Note that Lang 3.0 (and subsequent versions) use a different package (org.apache.commons.lang3) than the previous versions (org.apache.commons.lang), allowing it to be used at the same time as an earlier version.