Upstream software project

jakarta-commons-launcher

Javadoc for jakarta-commons-launcher

About jakarta-commons-launcher

Javadoc for jakarta-commons-launcher

This project links 4 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.jakarta-commons-launcher: recorded package coverageopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
jakarta-commons-launcher
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
opensuse-leap-16-0, opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Commons-launcher eliminates the need for a batch or shell script to launch a Java class. Some situations where elimination of a batch or shell script may be desirable are: * You want to avoid having to determining where certain application paths are, for example, your application's home directory. Determining this dynamically in a Windows batch script is very tricky on some versions of Windows or when softlinks are used on Unix platforms. * You want to avoid having to handle native file and path separators or native path quoting issues. * You need to enforce certain system properties, such as java.endorsed.dirs when running with JDK 1.4. * You want to allow users to pass custom JVM arguments or system properties without having to parse and reorder arguments in your script. This can be tricky or messy in batch and shell scripts. * You want to bootstrap system properties from a configuration file instead of hard-coding them in your batch and shell scripts. * You want to provide localized error messages, which is very tricky to do in batch and shell scripts.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 16.0

  1. Package jakarta-commons-launcher

    leap-16.0 (openSUSE Leap 16.0) (Development/Libraries/Java): A Cross-Platform Java Application Launcher

    1.1-bp160.1.11: noarch

    Source: jakarta-commons-launcher

  2. Source: jakarta-commons-launcher

openSUSE Tumbleweed

  1. Package jakarta-commons-launcher

    tumbleweed (openSUSE Tumbleweed) (Development/Libraries/Java): A Cross-Platform Java Application Launcher

    1.1-25.18: noarch

    Source: jakarta-commons-launcher

  2. Source: jakarta-commons-launcher

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.