Bug#987771: ITP: capsule-nextflow -- packaging and deployment tool for Java applications
Owner: Debian-med team <email@example.com>
X-Debbugs-Cc: firstname.lastname@example.org, email@example.com
* Package name : capsule-nextflow
Version : 1.1.0
Upstream Author : Paolo di Tommaso <firstname.lastname@example.org>
* URL : https://github.com/nextflow-io/capsule
* License : EPL-1.0
Programming Lang: Java
Description : packaging and deployment tool for Java applications
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.
It can contain JAR artifacts, dependencies and resources, native libraries,
the required Java Runtime Environment version, the Java Virtual Machine flags
required to run the application well, Java or native agents and more. In
short, a capsule is a self-contained JAR that knows everything there is to
know about how to run the application the way it is meant to run.
One way of thinking about a capsule is as a fat JAR on steroids (that also
allows native libraries and never interferes with your dependencies) and a
declarative startup script rolled into one; another, is to see it is as the
deploy-time counterpart to your build tool. Just as a build tool manages your
build, Capsule manages the launching of your application.
This package contains a fork of the original capsule project. This fork is
suited as a dependency of nextflow, which is a workflow engine needed in the
It will thus be maintained inside this team.