cstamas edited a comment on pull request #158: URL: https://github.com/apache/maven-resolver/pull/158#issuecomment-1068308628
@jebeaudet if you nuke local repo, then you can count the files (count + byte size). During dependency collection POMs are downloaded, the bigger the graph the more POMs are downloaded. With this PR you should end up with LESS POMs (present, hence downloaded) in local repository. The "resolved" result (classpath) OTOH should not be affected by this change, hence compile, packaging etc other times should not be affected. So in short, run times are not so "interesting", it is more the contents of local repository... (re my times: aside of total files/total bytes notable change among my result, I was also a bit "cheating" here, but I did mention it several times, that my "mvn bfs" is built from https://github.com/apache/maven/pull/635, hence "my mvn bfs" uses resolver-transpprt-http, hence the drastic time change as well, as I always nuke local repo and http transport is currently unbeatable by default wagon transport. But again, the times are not so important, the diff of downloaded POMs is they key here) -- 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
