Upgrading to the latest Mockito 2.x version has been enough in my
other projects to eliminate its Java-9 warnings/errors without any
code changes, but YMMV.
Cheers,
Peter
On 29 July 2017 at 07:44, Karl Heinz Marbaise wrote:
> Hi,
>
> +1 from me.
>
>
> Tested with JDK 9+180 the following Maven v
Yes, +1
On 28 July 2017 at 18:18, Robert Scholte wrote:
> Thanks for testing. Can I translate this to a +1 vote?
>
> Robert
>
>
> On Fri, 28 Jul 2017 02:04:40 +0200, Peter Ansell
> wrote:
>
>> The sha1 matches for me and the plugin (including requireJavaVersion)
&g
The sha1 matches for me and the plugin (including requireJavaVersion)
works under both Oracle JDK 8+u131 and Oracle JDK 9+177.
Thanks,
Peter
On 27 July 2017 at 06:58, Robert Scholte wrote:
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520
+1
Checksum for the source release matches the given sha1.
Plugin works as intended to create valid site (javadoc:javadoc) and
javadoc jars (javadoc:jar) using both JDK-8u131 and JDK-9b177
Only question is whether the Release Notes page on the staging site is
intentionally empty at this point in
Releasing the javadoc plugin with its Java 9 fixes in parallel would also be
great to have both of them ready to go on the GA date.
Cheers,
Peter
> On 11 Jul 2017, at 19:07, Dawid Weiss wrote:
>
> Hello there,
>
> Is there any schedule to release maven-enforcer with Java 1.9
> compatibility
GitHub user ansell opened a pull request:
https://github.com/apache/maven-enforcer/pull/24
MENFORCER-274 : Add check for version 9 in RequireJavaVersion
Adds an explicit regression check for Java-9 in the RequireJavaVersion test.
Note, the test already succeeds, this is
