Maven 3, and long build after switching mirror of central
Hello Maven users, User settings is configured to use a repository C1 on repo manager (Nexus) at H1 host as mirror of central. Local repo is clean. Project being built is a very simple maven project with pom packaging, which just lists latest versions of maven core plugins in pluginManagement section, and configures some of them. CLI build is started with package goal, Maven resolves/downloads plugins, build is successful. Then user settings are reconfigured so that repository C2 on repo manager (again Nexus) at H2 host is mirror of central. CLI build is started with clean package goals, Maven again resolves/downloads plugins, for every downloaded plugin 0 B at 0.0 KB/sec gets displayed, build is successful. This second build lasts almost five minutes (4:54.371s to be more precise). Is this normal? Project does not have any sources, code generation or anything similar, just plain pom file with core plugins. If it's likely repo manager (configuration) issue, will ask on Nexus mailing list. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3, and long build after switching mirror of central
started with clean package goals, Maven again resolves/downloads plugins, for every downloaded plugin 0 B at 0.0 KB/sec gets displayed, build is successful. This second build lasts almost five minutes (4:54.371s to be more precise). Is this normal? Project does not have any sources, code generation or anything similar, just plain pom file with core plugins. If it's likely repo manager (configuration) issue, will ask on Nexus mailing list. How long a given build will take while connecting to a given Nexus instance is highly (linearly) dependent on the state of cached artifacts in that particular Nexus instance. If H1 had all those Maven artifacts cached and H2 was empty, it may take 5 mins for H2 to download and store all the poms and jars etc that your build requires -- but then none got transferred to your local Maven build because you already had them all cached in your own local .m2 directory (thus the 0 B at 0.0 KB/sec -- if you were able to see the Nexus download monitor at the same time, it would show different numbers). By all means, forward this to the Nexus lists for verification and perhaps some suggestions on what logs to watch to debug this for yourself. But this explanation makes sense to me, and probably explains what you are seeing. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3, and long build after switching mirror of central
Yes, that was it, the other proxy repo on H2 was clean. Thanks for helping me understand! Regards, Stevo. On Tue, Feb 8, 2011 at 2:44 AM, Wayne Fay wayne...@gmail.com wrote: started with clean package goals, Maven again resolves/downloads plugins, for every downloaded plugin 0 B at 0.0 KB/sec gets displayed, build is successful. This second build lasts almost five minutes (4:54.371s to be more precise). Is this normal? Project does not have any sources, code generation or anything similar, just plain pom file with core plugins. If it's likely repo manager (configuration) issue, will ask on Nexus mailing list. How long a given build will take while connecting to a given Nexus instance is highly (linearly) dependent on the state of cached artifacts in that particular Nexus instance. If H1 had all those Maven artifacts cached and H2 was empty, it may take 5 mins for H2 to download and store all the poms and jars etc that your build requires -- but then none got transferred to your local Maven build because you already had them all cached in your own local .m2 directory (thus the 0 B at 0.0 KB/sec -- if you were able to see the Nexus download monitor at the same time, it would show different numbers). By all means, forward this to the Nexus lists for verification and perhaps some suggestions on what logs to watch to debug this for yourself. But this explanation makes sense to me, and probably explains what you are seeing. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
