Hi,
Nice catch, stupid me... how did we not catch it during review?
Let's be pragmatic: I fixed this stupid issue directly to master
> I wonder if it's feasible to add an integration test that checks
> that Maven home is the same before and after some build.
if you have an idea of an IT, don't h
Hi,
The current mvn startup script sets the "library.jansi.path" system
property to "${MAVEN_HOME}/jansi-native". But instead, as said in
MNG-6186, this should be "${MAVEN_HOME}/lib/jansi-native". This also
affects the Windows script. The result is that JAnsi is creating a
jansi-native directory
Hi Olivier,
assuming this bom file is not used by the reactor, it should be possible
to possible to generate it in the root pom and attach it with its own
GA[1][2].
The javadoc content says this piece of code is deprecated, probably
because it introduces some magic where it is hard to deter
