Asking Andrew. Maven is still using the old version 2.12.4 but this will be
changed, see https://issues.apache.org/jira/browse/MNG-6169
On Sat, Jun 29, 2019 at 5:05 PM Thomas Broyer wrote:
> On Sat, Jun 29, 2019 at 4:50 PM Tibor Digana
> wrote:
>
> > Where do we use dependency with groupId "org
On Sat, Jun 29, 2019 at 4:50 PM Tibor Digana wrote:
> Where do we use dependency with groupId "org.codehaus.mojo"?
>
I wasn't replying to the surefire part of the OP, Tibor; only about
org.codehaus.mojo groupId and whether those are "dead components".
Where do we use dependency with groupId "org.codehaus.mojo"?
Thx
Tibor
On Sat, Jun 29, 2019 at 3:18 PM Thomas Broyer wrote:
> Artifacts using the org.codehaus.mojo groupId does not mean they "come
> from" the mojo.codehaus.org forge.
>
> All the (maintained) plugins and libraries have found a ne
Hi James,
You’re using Google’s Maven repository mirror (the URL tells so). It’s
configured by your settings.xml. I would try switching back to Maven
Central by removing the mirror setting.
If switching back to Maven central solves the warnings, then it’s Google’s
mirror problem. If the warnings
Artifacts using the org.codehaus.mojo groupId does not mean they "come
from" the mojo.codehaus.org forge.
All the (maintained) plugins and libraries have found a new home at
MojoHaus, i.e. GitHub: https://www.mojohaus.org/, and they continue to be
published within the org.codehaus.mojo groupId.
O
The latest plugin is using maven-plugin-api:3.0. What version of plugin you
mean?
T
On Sat, Jun 29, 2019 at 8:31 AM Marlow, Andrew
wrote:
> Hello everyone,
>
>
>
> As we know, codehaus went dark some time ago, March 2015 in fact (see
> https://www.javaworld.com/.../codehaus-the-once-great-house-
