There is a preliminary test in [1] and the failure in [2].
The best I can do is to leave the IT as-is, put a max boundary 3.5.4)
and add a new IT for the Path solution. The unit test would be
assertFalse() accompanied with a new test for this issue.
Moreover, I will check for baseUri.startsWi
Hi Martin,
It is also a matter of numbers: I believe the current way of work of JPMS
with Maven is good enough and if there are issues, most of them should be
fixable. For me there's no reason to work on a proposal which is unlikely
to be implemented, since there are much more other issues
Hello Robert
Le 30/04/2018 à 21:00, Robert Scholte a écrit :
> All seems to fall back to an issue with the maven-javadoc-plugin. What
> if we try to fix that first?
>
That would help a lot. Getting Maven javadoc:aggregate goal to work
would address maybe 95% of the needs. But Javadoc is not the o
I don't see a new test[1][2], only rewrites to confirm there's no
regression.
I understand the issue, but we just need to be sure that nobody in the
future thinks that File.toURI() is short for File.toPath().toUri()
Robert
[1]
https://github.com/apache/maven/commit/43b34598629f086523a333
