-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Resolve Maven group id and artifact id from Maven properties #7309
Comments
That is, dependabot doesn't update |
Hi @michalvavrik I don't really understand what the issue is here? Are you saying that Dependabot doesn't update this? I have lots of Quarkus projects set up that way and Dependabot updates them just fine. |
Issue is that Dependabot didn't create single bump for this very dependency.
Yes.
I didn't know that, opened issue because I assumed that Dependabot doesn't handle this. In that case my only explanation is this line which makes sense (and I didn't mention it till now) and I'll close this issue if dropping it fixes the problem. Thanks for the link and info. |
You can see the |
no worry, that was the first thing I checked, thanks! |
Alright, we have it working now quarkus-qe/quarkus-test-framework#1001 (removing the ignore rule for plugin helped), sorry for the fuss and thank you for help. |
Is there an existing issue for this?
Feature description
We have got BOM like this
https://github.com/quarkus-qe/quarkus-test-framework/blob/692b6ed2f55d4a3258625c7b814a19f0ad8586f8/pom.xml#L78
as very often, we need to be able to use project with different Quarkus versions and make this change from CLI like this
mvn clean verify -Dquarkus.platform.version=3.0.1.Final -Dquarkus.platform.artifact-id=io.quarkus.platform
etc. It really depends on situation. However I didn't find a way to tell Dependabot to update Maven propertiesIt would be nice if Dependabot could automate this bump for us (it can be optional behavior in case you sense some troubles doing this be default...).
The text was updated successfully, but these errors were encountered: