[MNG-8751] Bad error message when unresolved expressions exist in POM #10324
Description
Lenny Primak opened MNG-8751 and commented
Maven (master) is more strict with unresolved expressions.
However, the error message it gives when this happens is bad. There should be a better error message:
Invalid Collect Request: null -> [ERROR] Invalid Collect Request: null -> [jakarta.platform:jakarta.jakartaee-api:jar:10.0.0-lp-nov6 (provided), com.flowlogix.depchain:integration-test:pom:58 (test), org.slf4j:slf4j-api:jar:2.0.17 (provided), org.slf4j:slf4j-jdk14:jar:2.0.17 (runtime?), fish.payara.arquillian:arquillian-payara-server-remote:jar:3.1 (test), org.seleniumhq.selenium:selenium-java:jar:4.32.0 (test), org.seleniumhq.selenium:selenium-grid:jar:4.32.0 (test)] < [central-mirror (https://nexus.hope.nyc.ny.us/repository/maven-public-jitpack, default, releases)]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the '-e' switch
[ERROR] Re-run Maven using the '-X' switch to enable verbose output
Reproducer:
$ git clone https://github.com/flowlogix/selenium-test
$ git checkout ef31c7e20b98acbb6454bf6597a2b8009fe164a7
$ mvn packageMaven version:
Apache Maven 4.0.0-rc-4-SNAPSHOT (f4c3fdd)
Affects: 4.0.0-rc-4
1 votes, 2 watchers