-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
maven version expanded #794
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
@cheister could you please review my PR? and also how can i get past the pipeline errors |
@knarukulla have you signed the CLA? I imagine that @cheister may be waiting until that's done before reviewing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
expand_make_variables
is marked as deprecated, but I can see this being useful since we don't actually know the variables we are replacing. LGTM.
Thank you for the PR!
👋 Hi @shs96c, is there a plan to cut a new release soon? I am interested in this change to (partially) replace the solution in #618 (comment). However, I have two questions related to this change:
|
We probably do need to expand the tag in |
We are working on the next release too: #831 |
I can file a PR for the |
I can take a look at that. |
Issue: #618
Solution:
Expand maven version using bazel variables to publishing maven artifact to repo.
bazel run --stamp
--define "maven_repo=<>
--define "maven_user=<>"
--define "maven_password=<>"
--define "maven_version=<>"
//src/main/java/com/xxx/example: