I don't expect any issues with 13-ea. I've already used it during my talks.
Since the plugin is pretty stable after several major release of Java, I
don't expect another plugin release soon, so better spend some time on
MCOMPILER-320[1] too.
Right now there's a fork, but it would be better to have the right
solution in our compiler-plugin.
But that means we need a complete demonstration of the issue. I'm still
hoping this can be solved without the proposed additionalCompilePathItems
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MCOMPILER-320
On Sat, 23 Mar 2019 23:34:19 +0100, Karl Heinz Marbaise
<[email protected]> wrote:
Hi Gary,
On 23.03.19 22:30, Gary Gregory wrote:
Make sure it works with Java 12 and 13 EA?
You know the build pipeline we are using:
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-compiler-plugin/job/master/
Usually we start to build with EA builds of JDK if the Rampdown Phase
one starts...? (@Robert Scholte?) Do we?
Kind regards
Karl Heinz Marbaise
Gary
On Sat, Mar 23, 2019, 17:22 Tibor Digana <[email protected]
<mailto:[email protected]>> wrote:
Hey Karl. feel free to start the release process. No objections
from my
side.
@Robert is there some more you want to add in the version 3.8.1?
T
On Sat, Mar 23, 2019 at 12:20 PM Tibor Digana
<[email protected] <mailto:[email protected]>>
wrote:
> Hi,
>
> All the issues for maven-compiler-plugin:3.8.1 is fixed.
>
https://issues.apache.org/jira/projects/MCOMPILER/versions/12343484
>
> Can we agree on cutting the release version?
> Do you see any reason to wait?
>
> I am very happy to see a new incremental compiler, see
> https://issues.apache.org/jira/browse/MCOMPILER-349
>
> Cheers
> Tibor
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
