Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: publish all Maven artifacts, not just one #1694

Merged
merged 1 commit into from
Jul 22, 2024

Conversation

SanjayVas
Copy link
Member

Unlike the build subcommand, the run subcommand of the Bazel CLI only operates on a single target.

@wfa-reviewable
Copy link

This change is Reviewable

@SanjayVas SanjayVas enabled auto-merge (squash) July 18, 2024 17:18
Copy link
Collaborator

@stevenwarejones stevenwarejones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @SanjayVas)

Unlike the `build` subcommand, the `run` subcommand of the Bazel CLI only operates on a single target.
@SanjayVas SanjayVas merged commit 6286147 into main Jul 22, 2024
4 checks passed
@SanjayVas SanjayVas deleted the sanjayvas-maven-publish branch July 22, 2024 15:23
ple13 pushed a commit that referenced this pull request Aug 16, 2024
Unlike the `build` subcommand, the `run` subcommand of the Bazel CLI only operates on a single target.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants