Hello,
it looks like maven-3.6.2 really introduced a non compatible change with
[core?] extensions and not just on polyglot-maven.
In my own core extension project (jgitver-maven-plugin), when using
maven-3.6.2, the ModelProcessor that I provide is not called anymore.
Hope that helps to track
Any volunteer to work on a fix?
Enrico
Il sab 14 set 2019, 10:08 Jonathan Chen ha scritto:
> Hi,
>
> I didn't find a matching issue, so I raised MNG-6765 so that it can be
> tracked.
> https://issues.apache.org/jira/browse/MNG-6765
>
> Cheers.
> --
> Jonathan Chen
>
> On Sat, 14 Sep 2019 at
Hi,
I didn't find a matching issue, so I raised MNG-6765 so that it can be tracked.
https://issues.apache.org/jira/browse/MNG-6765
Cheers.
--
Jonathan Chen
On Sat, 14 Sep 2019 at 19:47, Jonathan Chen wrote:
>
> Hi,
>
> Thanks for that. Is there a JIRA reference for this bug?
>
> Cheers.
> --
Hi,
Thanks for that. Is there a JIRA reference for this bug?
Cheers.
--
Jonathan Chen
On Sat, 14 Sep 2019 at 17:39, Jeff MAURY wrote:
>
> This is a know case between tycho pomless and maven 3.6.2
>
> Le sam. 14 sept. 2019 à 05:26, Jonathan Chen a écrit :
>
> > Hi,
> >
> > I'm currently
This is a know case between tycho pomless and maven 3.6.2
Le sam. 14 sept. 2019 à 05:26, Jonathan Chen a écrit :
> Hi,
>
> I'm currently attempting to build Eclipse 4.13 from source using
> maven-3.6.2, and I'm seeing these current failures:
> [INFO] Scanning for projects...
> [ERROR] [ERROR]
Hi,
I'm currently attempting to build Eclipse 4.13 from source using
maven-3.6.2, and I'm seeing these current failures:
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM
