bazelbuild / bazelbuild/rules_java

Provide a way of packaging separate layers into Java container after deprecation of rules_docker

Open
#160 3 comments 1 reaction 0 assignees View on GitHub
P3
Dominant language
Starlark
Stars
103
Forks
102
PR merge metrics
No merged PRs in 30d

Description

(It feels awkward to ask this question here, but it is a follow-up of [ this suggestion over at rules_oci ](https://github.com/bazel-contrib/rules_oci/issues/416#issuecomment-1832829593))

As the maintainers have decided that the rules_oci repository should remain language agnostic, it is quite unclear where to go with questions for language-specific containers, so following @alexeagle 's advice I am trying over here.

I would like to migrate from rules_docker to rules_oci, but the functionality to package depsets into separate layers has not been provided by the new rules ([_jar_app_layer_impl](https://github.com/bazelbuild/rules_docker/blob/8e70c6bcb584a15a8fd061ea489b933c0ff344ca/java/image.bzl#L178-L212) ).

Would it be possible to provide similar functionality in a `.defs` file in this repository, and could someone help me out in porting it?

Contributor guide

Open the contributing guide

Research direction

Start by reading the referenced _jar_app_layer_impl in rules_docker's java/image.bzl and the linked rules_oci discussion. Determine the intended home and scope for equivalent depset-to-layer packaging in this repository. Done means the requested Java container layering functionality is provided through a .defs file with a clear migration path from rules_docker.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
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.