OpenLiberty / OpenLiberty/liberty-tools-eclipse

Provide a single downloadable install archive (without any repository references)

Open
#332 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement high priority releng
Dominant language
Java
Stars
16
Forks
20
Avg merge
2d 9h
Merged PRs (30d)
16

Description

For environments where download access is managed more strictly, it could be helpful to provide Liberty Tools bundled along with its prerequisites in a single JAR archive.

Some questions:

UPDATES

Could this affect the visibility of the upstream dependencies with respect to updates? E.g. could it possibly be the case that by taking control of the content more directly via our feature installs the associated update sites are no longer visible within a "Check for Updates" operation?

If so, this would not necessarily cause any real world impact, the repository refs we have currently:

  • <repository-reference location="https://download.eclipse.org/jdtls/milestones/1.5.0/repository" enabled="true" />
  • <repository-reference location="https://download.eclipse.org/lsp4mp/releases/0.5.0/repository" enabled="true" />
  • <repository-reference location="https://download.eclipse.org/lsp4jakarta/releases/0.1.0/repository" enabled="true" />

are not URLs likely to receive updates. They're not 'latest' type of release URLS. So maybe this doesn't matter but would be helpful to generally understand.

LEGAL/METADATA

Does this affect any legal/metadata description we need to provide?

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.

Research direction

Start by reviewing how the current feature installs package prerequisites and declare the listed repository-reference entries. Investigate whether a single JAR would preserve update visibility and what legal or metadata descriptions it would require. Done means the archive format, update behavior, and metadata requirements are defined clearly enough to implement.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.