-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Experimental Maven goal to check for Quarkus platform and extension updates #19926
Conversation
devtools/maven/src/main/java/io/quarkus/maven/CreateProjectMojo.java
Outdated
Show resolved
Hide resolved
f9fbf37
to
e2cdad7
Compare
This is great - but Shouldn't we expose this as via the cli rather than adding mvn specific goal? |
Of course, the cli is the tool. This pr however is a quick attempt and I thought we could squeeze it in tomorrow's release. |
devtools/maven/src/main/java/io/quarkus/maven/CheckForUpdatesMojo.java
Outdated
Show resolved
Hide resolved
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building e2cdad7
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 16 #- Failing: extensions/amazon-lambda/deployment
! Skipped: docs extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 6 more 📦 extensions/amazon-lambda/deployment✖
|
…pdates Co-authored-by: Guillaume Smet <guillaume.smet@gmail.com>
e2cdad7
to
05b4d36
Compare
Failing Jobs - Building 05b4d36
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 11 #- Failing: integration-tests/elytron-undertow integration-tests/hibernate-orm-tenancy/connection-resolver integration-tests/mongodb-panache
📦 integration-tests/elytron-undertow✖
📦 integration-tests/hibernate-orm-tenancy/connection-resolver✖
✖
✖
📦 integration-tests/mongodb-panache✖
⚙️ JVM Tests - JDK 11 Windows #- Failing: extensions/amazon-lambda/deployment
! Skipped: docs extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 6 more 📦 extensions/amazon-lambda/deployment✖
⚙️ JVM Tests - JDK 16 #- Failing: integration-tests/hibernate-orm-tenancy/connection-resolver integration-tests/mongodb-panache
📦 integration-tests/hibernate-orm-tenancy/connection-resolver✖
✖
✖
📦 integration-tests/mongodb-panache✖
⚙️ Native Tests - Data1 #- Failing: integration-tests/hibernate-orm-tenancy/connection-resolver
📦 integration-tests/hibernate-orm-tenancy/connection-resolver✖
✖
✖
|
This is an experimental goal, in a sense that I wouldn't guarantee any backward compatibility at all. But I would still like to get it in to be able to test update discovery from projects that aren't using the latest platform and/or quarkiverse extension versions.
E.g. with this goal for a project based on the
quarkus-universe-bom
1.1.7.Final
e.g.:This command
mvn io.quarkus:quarkus-maven-plugin:999-SNAPSHOT:check-for-updates
will currently report:ATM, it should be considered as a low-level update info. It's not really instructions to follow. Ideally it should later be suggesting to change the relevant properties in the POMs and be in general more project-specific than what's displayed above.