On Tue, 22 Nov 2016 00:48:04 +0100, Jörg Schaible wrote:
Gilles wrote:
Hi.
Does someone know how to fix that?
See:
https://travis-ci.org/apache/commons-rng/jobs/177715168
Thanks,
Gilles
Delete your local repository (well, org/apache/commons/commons-rng)
and
you'll face the same. You cannot declare a dependency for a plutin
that does
not yet exist. Maven resolves the plugin's deps way earlier in the
reactor
before the it calculates the build sequence for the subprojects.
What I've been asking about for weeks is whether this ("build-tools")
use of a module is a valid one.
As I understand it, all configurations for the reports have been
bundled in that "module". Its use is _purely_ internal to the
maven build process.
So Artem's idea looked fine _iff_ maven can indeed handle such
"pre-dependencies".
If not, this "build-tools" module must disappear (as there is
nothing to release about it, once "mvn site" has run).
If this is the case, how should I go about to repair the build?
Thanks,
Gilles
And you cannot rely on the fact the the build tools are actually
build
first. AFAICS the reactor will not take the dependencies to plugins
into
account when it calculates the build sequence. The list of modules in
the
parent has to be unique only, the sequence is based on the dependency
calculation. If you are using multiple threads to build, nobody will
wait
for the build tools to complete.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
