IDE support is still catching up. At least in VS code, the Java
extensions produce errors and failed imports, which slows development.
See also: https://github.com/eclipse-m2e/m2e-core/pull/2053
Markos
On 12/25/25 20:44, Richard Zowalla wrote:
Hi,
Thanks for starting this thread.
I am fine with running in Maven 4 RC as long as we can run a release, i.e. we
would need to do a dry run, check the staging repo and it's contents + verify
the source release.
I know IDEA already supports Maven 4. What about Eclipse and Netbeans?
If all looks good, we can do the change, IMHO.
Gruß
Richard
Am 25. Dezember 2025 17:06:22 MEZ schrieb Markos Volikas <[email protected]>:
Hi all,
In 1716 <https://github.com/apache/stormcrawler/pull/1716>, we prepared for
migrating to Maven 4. The PR includes the necessary POM changes and a step for
installing the latest Maven 4 RC in the Maven GitHub workflow.
As Richard mentioned, we could either wait for the official release before
merging the changes or switch to building with the latest Maven 4 RC right now.
One possible issue I see with the latter is that breaking changes might be
introduced in the next RCs, in which case we will have to reiterate the changes
in additional PRs.
What do you think?
Best,
Markos
