bazel-contrib / bazel-contrib/rules_jvm_external

FR: generate linkable alternative target for neverlink jars (reopen)

Open
#399 0 comments 4 reactions 0 assignees View on GitHub
type: feature request
Dominant language
Java
Stars
373
Forks
301
Avg merge
7d 17h
Merged PRs (30d)
3

Description

Following issue #185

We actually have the same issue at Wix and we would love to have the same some built in solution for linkable target. We prefer not to have multiple maven_install calls as it generates two different dependency trees.

How about generating a linkable target under `@maven//linkable:`? e.g: `@maven//linkable:javax_servlet_javax_servlet_api`

The content of it would be similar to the BUILD file in the root of the generated external repository but the rules would not have `neverlink=True`?

We would love to implement it, if we agree that it's a good solution.

cc: @liucijus @ittaiz @natansil , @jin

Contributor guide

Open the contributing guide

Research direction

Start by reading issue #185 and the generated external repository's root BUILD file, both referenced in the issue. Determine how a @maven//linkable: target should be generated without neverlink=True while preserving one dependency tree; done means the proposed linkable targets are available for the requested artifacts and the existing targets remain intact.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.