Looks good to me.
I expect some trouble when moving plugins from Maven 3.0 to 3.1.0, so I've
started a wiki page[1] with the first known issue and solution.
Robert
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=155749857
ps. As long as Maven isn't bundled with its own
On Wed, 3 Jun 2020 at 4:56 pm, Michael Osipov wrote:
> Am 2020-06-03 um 03:00 schrieb Olivier Lamy:
> > Hi
> > Please comment or (not) complain on this change.
> > html version https://maven.apache.org/developers/compatibility-plan.html
>
> LGTM
>
> > PS: FYI Eclipse will be jdk11 in September
>
Thanks for reading this
On Wed, 3 Jun 2020 at 6:28 pm, Anders Hammar wrote:
> A few comments:
>
> 1. I think we should separate the prerequisites for Maven core and those
> for our plugins.
> 2. Do users really care about "Maven Plugin API"? I think that an end user
> would like to know what
A few comments:
1. I think we should separate the prerequisites for Maven core and those
for our plugins.
2. Do users really care about "Maven Plugin API"? I think that an end user
would like to know what version of Maven (core) that a plugin will work
with.
/Anders
On Wed, Jun 3, 2020 at 3:01
Am 2020-06-03 um 03:00 schrieb Olivier Lamy:
Hi
Please comment or (not) complain on this change.
html version https://maven.apache.org/developers/compatibility-plan.html
LGTM
PS: FYI Eclipse will be jdk11 in September
https://www.eclipse.org/lists/cross-project-issues-dev/msg17532.html
I
Hi
Please comment or (not) complain on this change.
html version https://maven.apache.org/developers/compatibility-plan.html
cheers
Olivier
PS: FYI Eclipse will be jdk11 in September
https://www.eclipse.org/lists/cross-project-issues-dev/msg17532.html
On Wed, 3 Jun 2020 at 10:56, wrote:
> This
