Hi Romain,
the dependencyOverrides element is an addition. While it shares some
characteristics, it does not duplicate the dependencyManagement element. In
fact, it's a part of it. Come to think of it, it may even be ok to locate/place
it "next to" the dependencyManagement element, thus making
michael-o merged pull request #252:
URL: https://github.com/apache/maven-site/pull/252
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
rosti-il opened a new pull request #252:
URL: https://github.com/apache/maven-site/pull/252
UTF8 is an illegal name of the UTF-8 encoding. The dash is mandatory.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Tamás Cservenák, Olivier Lamy, Enrico Olivelli, Karl
Heinz Marbaise, Robert Scholte, Sylwester Lachiewicz, Arnaud Héritier,
Dan Tran, Tibor Digana
PMC quorum: reached
I will promote the artifacts to the central repo,
Hmm, I probably miss a thing but it looks like you just redid
dependencyManagement but duplicating it you created a new issue: how to
override in the override block?
Only neat way I see to handle that is to drop the transitiveness of the
override block which would defeat a lot dependency usage so
Hi Michael,
thank you for your answer.
An interesting thought. It never occurred to me that a global exclusion would
help in a similar way, but then again, global excludes aren't a thing, yet (are
they?). I think excluding globally and including a specific dependency as a
replacement is not
