[Request] Liberica NIK

Open
#467 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

No manifest, test, or entry-point file is named. Start by checking the Liberica Native Image Toolkit homepage and download link for the current stable version and installation details, then compare the request with existing Java packages in the bucket; done means the package is available through the bucket with the requested version and standard installation.

Written by the indexing model from the issue text.

Description

Package Request

Criteria

For a package to be acceptable in the Java bucket, it should be:

  • a runtime environment or software development kit for Java
  • a reasonably well-known and widely used developer tool (e.g. if it's a GitHub project, it should have at least 500 stars and 150 forks)
  • the latest stable version of the program
  • the full version i.e. not a trial version
  • a fairly standard install (e.g. uses a version-specific download URL, no elaborate pre/post install scripts)
  • downloadable without having to sign in or use user-dependant cookies
Information

Name: Liberica Native Image Toolkit

Description: A versatile tool for accelerating your applications. Liberica NIK is a multilingual tool that transforms your applications into performant native images. Based on GraalVM Open Source

Homepage: https://bell-sw.com/liberica-native-image-kit/

Download link(s): https://bell-sw.com/pages/downloads/native-image-kit/

Some indication of popularity/repute: Based on GraalVM and combine with Liberica JDK up to Full profile. Maintained by BellSoft which is one of the OpenJDK community contributor.

License: GPL

Dominant language
PowerShell
Stars
314
Forks
111
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ScoopInstaller/Java

All issues in ScoopInstaller/Java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.