cstamas commented on pull request #23: URL: https://github.com/apache/maven-artifact-transfer/pull/23#issuecomment-828750815
So, in the meanwhile (as we "facilitate" the Apéritif), the plan in short: * return maven 3.0 support * explode m-a-t into modules: m-a-t contains "api" and have a providers for maven3.0, maven3.1, maven4.0...(4 not really needed yet), m-a-t pulls in providers it knows about, so consumer still "just" depends on m-a-t, but they get all providers pulled in (no overlaps or having org.sonatype and org.eclipse on CP) * for this to work, providers will use provided scope of maven internals and aether/resolver (basically each provider will use deps it's maven provides as provided) * m-a-t defines all the API (as now), and providers provide SISU components implementing API using 3,0, 3.1 and so on * this makes all the reflection not needed, and other hoops and loops as well, simplifies development as in each provider you code "cleanly" against given maven version and it's surroundings * make Delegator "smarter" how to select what to lookup (similar as now, in this PR, but smarter) -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
