[WIP] move to org.apache.maven package

[olamy]

trafficstars

• bump version to 2.0.0-SNAPSHOT
• move to package org.apache.maven.resolver, bump version to 2.0.0

[michael-o]

Not now, please read: https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-MavenResolver

[olamy]

Not now, please read: https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-MavenResolver

why not using the 4.x window for this as well??? sounds definitely a good target.. or we have to wait too long for this...

It;s just a package change so really not much compared to all other changes included in 4.x

you guys shouldn;t be scared of package change?

[olamy]

@michael-o @cstamas the goal is to fix the biggest aberration we still have in our code base! Still using org.eclipse package in an Apache project distributed under groupId org.apache.maven
That's still definitely an aberration! Even eclipse has been faster to move from javax. to jakarta. Still in WIP as I have to remove ServiceLocator. But frankly we should have done this for MANY years...

[laeubi]

@cstamas this should be tagged 2.0 as well!

[cstamas]

It depends, we can do this only when resolver is completely sealed off from anything else than maven core (so when Maven 4 API is the only thing reachable for plugins). So, it may mean even 3.0...

[HannesWell]

The Import-Package specification added in https://github.com/apache/maven-resolver/pull/520, should be adapted in this PR before it lands.

[cstamas]

This PR is scheduled for Resolver 3.0.0, so in far future.