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

Use <parameters>true</parameters> instead of <compilerArgs><arg>-parameters</arg></compilerArgs> #41793

Merged
merged 1 commit into from
Jul 10, 2024

Conversation

turing85
Copy link
Contributor

@turing85 turing85 commented Jul 9, 2024

Since https://issues.apache.org/jira/browse/MCOMPILER-413 has been fixed with maven maven-compiler-plugin version 3.9.0, we no longer need this workaround.

Copy link

quarkus-bot bot commented Jul 9, 2024

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

  • description should not be empty, describe your intent or provide links to the issues this PR is fixing (using Fixes #NNNNN) or changelogs

This message is automatically generated by a bot.

@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/documentation area/maven area/platform Issues related to definition and interaction with Quarkus Platform labels Jul 9, 2024

This comment has been minimized.

@turing85 turing85 force-pushed the feature/parmeters-in-compile-plugin branch from 2cfe16f to a1943fb Compare July 9, 2024 19:12

This comment has been minimized.

This comment has been minimized.

@manofthepeace
Copy link
Contributor

I think quarkus is still built with 3.8.6, see here

<maven.min.version>3.8.6</maven.min.version>

It is in the process of being bumped here; but getting some issues. #41648

@gastaldi
Copy link
Contributor

I'm confused: Is 3.9.0 the Maven Core or the Maven Compiler plugin version? If it's the later, we're in 3.13.0 already

@manofthepeace
Copy link
Contributor

Right... I got confused. This should be the compiler plugin version. Please ignore my previous message.

@gsmet gsmet force-pushed the feature/parmeters-in-compile-plugin branch from a1943fb to ef216fe Compare July 10, 2024 07:32
@gsmet
Copy link
Member

gsmet commented Jul 10, 2024

I triggered another CI run as the failures in Maven Tests - JDK 17 are a bit odd.

Copy link

quarkus-bot bot commented Jul 10, 2024

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit ef216fe.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

@turing85
Copy link
Contributor Author

I triggered another CI run as the failures in Maven Tests - JDK 17 are a bit odd.

Seems like Maven Tests - JDK 17 succeeded this time 🙂

Copy link

quarkus-bot bot commented Jul 10, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit ef216fe.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 devtools/cli

io.quarkus.cli.plugin.PluginCatalogServiceTest.shouldSyncWhenProjectFileIsNewerThanCatalog - History

  • expected: <true> but was: <false> - org.opentest4j.AssertionFailedError
org.opentest4j.AssertionFailedError: expected: <true> but was: <false>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
	at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:31)
	at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:183)
	at io.quarkus.cli.plugin.PluginCatalogServiceTest.shouldSyncWhenProjectFileIsNewerThanCatalog(PluginCatalogServiceTest.java:109)

⚙️ JVM Tests - JDK 17 Windows

📦 integration-tests/grpc-hibernate

com.example.grpc.hibernate.VertxBlockingRawTest.shouldAdd - History

  • Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in com.example.grpc.hibernate.BlockingRawTestBase was not fulfilled within 30 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:975)
	at com.example.grpc.hibernate.BlockingRawTestBase.shouldAdd(BlockingRawTestBase.java:59)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)

Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

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

Thanks, very nice cleanup!

@gsmet gsmet merged commit aaf2960 into quarkusio:main Jul 10, 2024
55 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.13 - main milestone Jul 10, 2024
Copy link

🙈 The PR is closed and the preview is expired.

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/maven area/platform Issues related to definition and interaction with Quarkus Platform triage/flaky-test
Projects
Development

Successfully merging this pull request may close these issues.

4 participants