Love the work here - I'll definitely be keen on trying this out and see how it
interacts with our tiles-maven-plugin.
Regarding this "reactor" bit tho - just because a module is in the reactor,
doesn't always mean it has the same parent - the version of the dependency
could be elided if the parent version matched AND that dependency is part of
the reactor.
However, I have seem people use reactors purely as build-coordinators, and not
always used. I'd much rather seeing them stay - esp. if using version ranges (
we force [] ranges for instance ).
Mark
On 24/06/20, 9:20 AM, "Matthieu BROUILLARD" <matth...@brouillard.fr> wrote:
> dependencies that are part of the reactor don't need a version anymore
What is meant here ? Is it that in a multimodule project a dependency from
a module to another of the same multimodule does not need the version ? For
example when having an api and impl in the same multimodule, the impl will
not require the version of the api?
