Re: [CANCELLED] [VOTE] Release Apache Maven Shared Component: Maven Artifact Transfer Version 0.13.0
so after bisecting the issue in artifact-transfer I found the problem..
Revert "[MSHARED-817] Change eclipse aether dependency scope to provided"
This reverts commit 5d86480fcdf4f7ae779aec9c7444ad7b709eaa04.
Using this will run fine with maven-deploy-plugin with all IT's
ok...which fails several IT's in maven-deploy-plugin if using
artifact-transfer without the revert...
Related to that there was a discussion on GitHub about the change in
artifact-transfer which is related to ...I'm diving more into
that...and trying to find out what the real issue is based on that
commit. Changing the scope from compile to provided of
org.eclipse.aether:aether-util which contains the missed class
(SubArtifact.class) or is it related no more shading and transporting
that class as part of artifact transfer...
What I've understood so far is that shading this class makes it working
with Maven versions from 3.1.1 up to 3.3.3(?) related to ...which is
related to the part that it has been excluded via
Currently I'm figuring out why some core IT's are failing on my machine
(Mac OS)...needs more testing...(investigating).
Furthermore it showed that we need more IT's in artifact-transfer to see
such issues earlier...