On 2017-05-02 12:06, Julian Reschke wrote:
Hi there,
I just noticed that
mvn javadoc:javadoc
once again fails on trunk. This will be a problem when we'll get to
release 1.7.0.
Also note that "mvn release:prepare" is even more picky, as it also
tests non-aggregate Javadocs, so referencing something in a different
subproject will only work when there's an actual project dependency.
Best regards, Julian
This can be tested using
mvn release:prepare -DdryRun=true
FWIW, some of the errors may be caused by the recent refactoring work.
In any case, if we want to make 1.7.* releases, we'll have to fix this
(or skip javadoc generation when releasing, which is kind of lame).
Best regards, Julian
