Howdy, part2: now ITs got full isolation (from user env that runs them). This means that ITs are running in their own (dedicated and fully controlled) $HOME. The flipside: Maven IT suite (the one in Maven repo) can be run ONLY with Maven 3.9+ (local repo tail support required). Which is IMO fine, as older maven versions can still be used with old ITs (in maven-integration-tests repo).
Thanks T On Thu, Dec 5, 2024 at 5:12 PM Tamás Cservenák <ta...@cservenak.net> wrote: > > Howdy, > > just a heads up, as Maven ITs got quite a change(s). For starters, the > "embedded" profile is gone, as it is the default now. If you want > "forked" execution (slow but most isolated), use the new "forked" > profile. > > Second, maven-verifier and maven-shared-utils are gone from the IT classpath. > > Maven4 has now a new library called maven-executor that is used > (almost as a drop-in replacement) for maven-verifier. This is a > no-dependency and reusable library to run Maven, along with some > helpers (kinda functional equivalent of Verifier but with proper > support for Maven 3 and Maven 4). > > As a side-effect of these changes, Verifier-equivalent in ITs got > _removed_ all the ancient "path trickery" code (those to kinda > calculate an artifact or metadata path in local repository), all these > queries are now delegated to real maven (see maven-executor). Ultimate > goal is to open up for possibilities like use of split repositories in > ITs, something good old Verifier with those path calculations and > assumptions could never do. > > Have fun! > T --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
