[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#987946: ITP: capsule-maven-nextflow -- packaging tool for Java applications with Maven coordinates

Package: wnpp
Severity: wishlist
Owner: Debian-med team <debian-med@lists.debian.org>
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-med@lists.debian.org

* Package name    : capsule-maven-nextflow
  Version         :
  Upstream Author : Paolo di Tommaso <paolo@seqera.io>
* URL             : https://github.com/nextflow-io/capsule-maven
* License         : EPL-1.0
  Programming Lang: Java
  Description     : packaging tool for Java applications with Maven coordinates

A capsule is a single executable JAR that contains everything an application
needs to run either in the form of embedded files or as declarative metadata.
Maven Capsule is a capsule that allows the creations of capsules that, instead
of embedding their dependencies, download all or some of them from a Maven
repository. The dependencies are downloaded, cached locally, and shared among
other capsules that also depend on them. In addition, this capsule allows
specifying capsule metadata in a POM file in addition to the manifest.

A capsule with the Maven caplet that has all (or almost all) of its
dependencies downloaded rather than embedded is known as a "thin" capsule (as
opposed to a "fat" capsule, which embeds all of its dependencies). In fact, a
capsule may not contain any of the application's classes/JARs at all. Instead,
the capsule's manifest may contain these attributes alone (and no files in the
capsule JAR besides the manifest). When the capsule is launched, the newest
available version of the application will be downloaded, cached and launched.

This package contains a fork of the original capsule-maven project. This fork
is suited as a dependency of nextflow.

Reply to: