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,
Not sure how to do that in a non hackhish way.
My current goal: generate a bom style pom with all reactor projects in
dptMngt section.
As people are lazy to write dptMngt section in theirs poms they delegate to
others with this pom.
So as I'm lazy too I don't want to write/maintain this pom
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
