just a follow up on this one: > > > > A bit of research I came across this issue with the Maven Assembly plugin. > > http://jira.codehaus.org/browse/MASSEMBLY-424 >
I've posted some comments on this issue, but it basically comes down to a process fork per dependency which is a bit ScalabilityYucky(tm). It will do this multiple times for a single jar because the hbase modules are interrelated (they end up sharing a big chunk of the dependency space). We're in a hard place here because going back to beta-1 of the plugin would require some rework of the pom.xml to match the required syntax for that version. For now though stack is rightly sticking with beta-5 for now, sluggish though that is. One other way we could do to speed this up is now look at the dependency tree and start considering setting up exclude rules for those transitive dependencies you guys just know is not needed. By removing a jar, we reduce at least one, probably multiple process forks. I think if someone could inspect the 'lib' directory of the tar ball generated by mvn and say "hey, these X jars can just go" I or someone else can easily add the exclusions. thoughts? Paul
