So far it was buildable ONLY with Java 17, but only due
single IT: it used old Quarkus version that refused to
work on Java 21.
Ported updates from mvnd master and now mvnd-1.x branch
can also be build without any problem with Java 21.
Changes:
* no source changes
* (build) expel all versions from child modules: they must be all top level depMgmt or pluginMgmt
* (build) Top POM contains GAVs while child modules GA+scope. This tremendously simplifies maintenance.
* (javadoc) fix Javadoc errors
Updates:
* use latest Maven 3.9.8-SNAPSHOT (TS locked version, controlled deploy by me)
* AssertJ 3.26.0
* Takari Smart Builder 0.6.6
* Sisu 0.9.0.M3
* maven wrapper 3.3.2 w/ scripts
This brings mvnd-1.x in "releasable" state (once Maven 3.9.8 is out).
(same as on master, align with master)
Changes:
* ~roaster 2.29.0.Final~ (bytecode is banned by enforcer, is newer than allowed)
* testcontainers 1.19.8
* picocli 4.7.6
* jline 3.26.1
* javassist 3.30.2-GA
Most of cumulative things dependabot reported, plus more.
Changes:
* use plugins from parent (instead to double-maintain them here as well)
* general cleanup, add property where there are 2+ uses for it
* update plugins not present in parent
* non-key dependencies (maven3, maven4, graalvm not touched) updates
Port Maven 3.9.7 config and new properties (session.root/top)
into Daemon m39.
The IT got this property as it triggers exception (failure)
if mvn39 could not "discover" top directory.
Fixes#910
* Add configuration to send build scans to https://ge.apache.org
* Add `.mvn` directories to IT tests projects that lack one
Some of the integration tests to do not have `.mvn` directories and
search up the project structure until they find the `.mvn` directory
of the root project.
This change adds `.mvn` directories with empty `maven.config` files so
that the sample projects in VCS will be as close as possible to those
executed during integration testing
* Make the default (non-native) build work again
* the renamed test is supposed to use the native binary, but it was
being picked up by surefire, because of its name. For non-native builds
(e.g. without -Pnative) the test would fail as the native
binary does not exist
* Add GitHub job for for default (non-native) build
* Fix core export provider
Since https://github.com/apache/maven/pull/616, the default
CoreExportProvider no longer uses the provided CoreExports,
but instead tries (and fails) to discover them itself.
This change fixes that by providing our own custom instance
of CoreExportProvider. This allows core extension to contribute
exported artifacts and exported packages again, like it used to
do before the Maven 4.x upgrade.
* Add integration tests for API-providing extensions
