Great! Thanks for your answer. I didn't imagine there's another repository for this.
Looks like many of them are pulled in when I pull "maven-resolver-provider" and ASF license has been applied though the package name still starts with "org.eclipse". While I still love to hear more information it definitely helps. Thanks again! 2019년 3월 27일 (수) 오후 5:20, Enrico Olivelli <[email protected]>님이 작성: > Il mer 27 mar 2019, 08:25 Jungtaek Lim <[email protected]> ha scritto: > > > Hi devs, I'm Jungtaek Lim, PMC member of Apache Storm. > > > > Maybe it's a question for user, but mostly regarding license and > migration > > status of maven-artifact so sending here. Please kindly guide me if Maven > > community think it would be better to go through user mailing list. > > > > Apache Storm leverages Aether to pull transitive dependencies in runtime, > > which I think is EPLv1 (category B) - which I just reminded since we now > > deal with licenses. > > > > I got to know that Aether had a IP clearance and being included to Maven, > > which is great and I was planned to migrate Aether usage to > maven-artifact, > > > > We have now maven resolver which is a fork of aether. > But I have not followed the transition, the others on the list will have > more insight. > > Hope that helps > Enrico > > but I still see some of classes/packages (even in maven-core) Maven refers > > Aether as eclipse package which classes are also referred in Apache > Storm. > > (mostly spi, transport, etc.) > > > > Does it mean only part of things are migrated to Maven, and we still need > > to pull Aether with explaining their license? > > > > Thanks in advance, > > Jungtaek Lim (HeartSaVioR) > > >
