olamy commented on PR #31:
URL:
https://github.com/apache/maven-install-plugin/pull/31#issuecomment-1173601559
> > As an Apache project we do not own the package `org.eclipse.aether` so
we cannot promote the use of such package distributed in a `org.apache.maven
groupId`. This was supposed to be a temporary transitional phase. It's now
almost 7 years the project has been moved here. So as a transition phase we had
enough time to change this aberration from our source code. This usage should
be dead already after so many years. It looks to moving backward with such
change.. if the goal is remove some old dependencies we don't like (e.g the
dependencies pulled by m-a-t) we can certainly exclude:
> > ```
> > <artifactId>maven-artifact-transfer-maven-3.0.x</artifactId>
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > And even drop this module from our source code if we don't want to keep
supporting it. But the history of the source here at Apache is remove the usage
of org.eclipse as a package we distribute which again is totally wrong and we
cannot keep promoting.
>
> Stop spreading FUD man, you personally voted +1 on threads "[VOTE] Accept
the Aether code into the Maven project" and also on "[IP CLEARANCE] Aether,
renamed to Maven Artifact Resolver" on private ML (unsure could I link these as
archives for private ML are not public). Hence, due those two before, I bet you
got mails from thread "Trademark requests from Apache Maven regarding Aether"
as well, also on private ML (same ML as those two before). In short,
"distributing org.eclipse.aether" packages IS NOT WRONG, The Eclipse Foundation
granted us usage of that namespace.
I do not see really FUD and I'm prefectly aware of this acceptation of this
**temporary** package naming. My point has nothing to do with the history on
accepting some code. Please do not make confusion with my concern.
We created and agreed on m-artifact-transfer to hide all the previous
package changes and the future changes.
I just see the package `org.eclipse.aether` as deprecated already even
before m-artifact-transfer was created.
Again the current/previous package implementation is **temporary** and we
will change it by a renaming from org.eclipse.aether to org.apache.maven. and
we will provide a new API as well with 4.x
So plugins maintainers do not have to worry about the real internal and
obviously m-artifact-transfer will be de-facto deprecated when we will have
maven 4.x api and/or resolver package renaming.
If your concern is the possible m-artifact-transfer. Frankly since this has
been created there were not many really....
And we can definitely mark it as deprecated..
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
