bazelbuild/bazel

Mark module_extension or tag_class deprecated

Open

#24,843 opened on Jan 7, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (25,384 stars) (4,465 forks)batch import
P3help wantedteam-ExternalDepstype: feature request

Description

Description of the feature request:

Add a flag to mark module extensions or single tag classes deprecated and print a warning to the user when used.

Which category does this issue belong to?

Core

What underlying problem are you trying to solve with this feature?

Help users migrate away from deprecated features.

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Contributor guide

Tech stack
java
Domain
build system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Java knowledgeBazel internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests adding a deprecation mechanism for module extensions and tag classes in Bazel. The implementation likely involves modifying Bazel's core in Java, possibly in the 'src/main/java/com/google/devtools/build' directory. Existing deprecation patterns in Bazel should be examined to understand how deprecated warnings are currently issued. Since no pull requests are linked, the contributor should start by discussing the approach with maintainers.