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

Adjustments for the info and update commands #22999

Merged
merged 1 commit into from
Jan 21, 2022

Conversation

aloubyansky
Copy link
Member

Adjustments following feedback on #22979

  • Add 'experimental' warning to the info and update commands
  • use a single instance of the catalog resolver for the update (fixes Looking for the newly published extensions in registry.quarkus.io logged twice)
  • make sure update to the current platform version isn't suggested (e.g Update: io.quarkus.platform:quarkus-bom:pom:2.6.2.Final -> 2.6.2.Final)

@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/gradle Gradle area/maven area/platform Issues related to definition and interaction with Quarkus Platform labels Jan 19, 2022
@aloubyansky
Copy link
Member Author

About Instead of "Recommended Quarkus platform BOM updates" should we write "To follow latest recommended Quarkus platform:" ?
I see what you mean "to follow... do this" but I am not yet sure it's better. We probably need to have a good discussion on the whole presentation part, given that we all agree the phrasing and formatting isn't easy to follow.

@quarkus-bot
Copy link

quarkus-bot bot commented Jan 19, 2022

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 306e21a

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleKotlinProjectDevModeTest.main line 22 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference was not fulfilled within 3 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

@gsmet
Copy link
Member

gsmet commented Jan 19, 2022

@aloubyansky were you able to improve a bit the ordering of things to update?

@aloubyansky
Copy link
Member Author

No, I haven't yet. I can look into that and add it to this change.

@aloubyansky
Copy link
Member Author

Fixed the ordering.

@quarkus-bot
Copy link

quarkus-bot bot commented Jan 20, 2022

This workflow status is outdated as a new workflow run has been triggered.

🚫 This workflow run has been cancelled.

Failing Jobs - Building b6bf2f6

Status Name Step Failures Logs Raw logs
Initial JDK 11 Build ⚠️ Check → Logs Raw logs
Attach pull request number ⚠️ Check → Logs Raw logs
CI Sanity Check ⚠️ Check → Logs Raw logs

@quarkus-bot
Copy link

quarkus-bot bot commented Jan 20, 2022

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building b00e8a7

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Build Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleKotlinProjectDevModeTest.main line 22 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference was not fulfilled within 3 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleKotlinProjectDevModeTest.main line 22 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference was not fulfilled within 3 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

io.quarkus.gradle.devmode.MultiModuleNamedInjectionDevModeTest.main line 21 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in io.quarkus.test.devmode.util.DevModeTestUtils that uses java.util.function.Supplier, java.util.function.Supplierjava.util.concurrent.atomic.AtomicReference, java.util.concurrent.atomic.AtomicReferencejava.lang.String, java.lang.Stringboolean was not fulfilled within 1 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:164)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)

@aloubyansky
Copy link
Member Author

Added update instructions for extensions that are moved in to/out of the platform between releases.

@quarkus-bot
Copy link

quarkus-bot bot commented Jan 20, 2022

This workflow status is outdated as a new workflow run has been triggered.

🚫 This workflow run has been cancelled.

Failing Jobs - Building 86ae1e2

Status Name Step Failures Logs Raw logs
Initial JDK 11 Build ⚠️ Check → Logs Raw logs
Attach pull request number ⚠️ Check → Logs Raw logs
CI Sanity Check ⚠️ Check → Logs Raw logs

@@ -34,6 +34,9 @@ public QuarkusInfo() {

@TaskAction
public void logInfo() {

getProject().getLogger().warn("This task is experimental, its options and output might change in future versions");
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
getProject().getLogger().warn("This task is experimental, its options and output might change in future versions");
getProject().getLogger().warn("quarkus info is experimental, its options and output might change in future versions");

In maven output this comes possibly many many lines away from what you just executed thus better to be explicit.

@@ -55,6 +55,9 @@ public QuarkusUpdate() {

@TaskAction
public void logUpdates() {

getProject().getLogger().warn("This task is experimental, its options and output might change in future versions");
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
getProject().getLogger().warn("This task is experimental, its options and output might change in future versions");
getProject().getLogger().warn("quarkus update is experimental, its options and output might change in future versions");

@@ -20,6 +20,12 @@
@Mojo(name = "info", requiresProject = true)
public class InfoMojo extends QuarkusProjectStateMojoBase {

@Override
protected void validateParameters() throws MojoExecutionException {
getLog().warn("This task is experimental, its options and output might change in future versions");
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
getLog().warn("This task is experimental, its options and output might change in future versions");
getLog().warn("quarkus info is experimental, its options and output might change in future versions");

@maxandersen
Copy link
Contributor

Looks good - added just comment to be explicit.

A few quirks I found.

mvn running update on a newly created project it prints:

[INFO] Recommended Quarkus platform BOM updates:

nothing else - maybe have a "Project extensions are aligned with the platform. No recommendations found." instead?

On how to word it, I'm wondering if just write about aligned with platform vs non-aligned with platform when it comes to version differences.?

Copy link
Contributor

@maxandersen maxandersen left a comment

Choose a reason for hiding this comment

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

looks good just be more explicit to the user.

…ngle instance of the catalog resolver for the update, make sure update to the current platform version isn't suggested
@aloubyansky
Copy link
Member Author

All fixed.

Copy link
Contributor

@maxandersen maxandersen left a comment

Choose a reason for hiding this comment

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

lgtm

@aloubyansky aloubyansky merged commit 53e5033 into quarkusio:main Jan 21, 2022
@quarkus-bot quarkus-bot bot added this to the 2.8 - main milestone Jan 21, 2022
@gsmet gsmet modified the milestones: 2.8 - main, 2.7.0.Final Jan 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/documentation area/gradle Gradle area/maven area/mongodb area/platform Issues related to definition and interaction with Quarkus Platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants