On Fri, Jun 8, 2012 at 3:29 PM, Roman Shaposhnik <[email protected]> wrote: > Still, I really think we should address this. Here's a JIRA that > tracks the effort: > https://issues.apache.org/jira/browse/BIGTOP-276 > this is clearly post Bigtop 0.4.0 but it could very well make it into > Bigtop 0.5.0. > > Of course, this is half of the problem -- the other half is making sure > that we can harmonize the versions of all the dependencies between > the projects. We do that in CDH (via patching poms, etc) but haven't > done anything like that in Bigtop yet. > >> How this would be handled at the OS level is each common dependency >> would be factored out into a library package. > > I'm keeping an eye on what Linux vendors do to address this issue. Here's > a blog post that is well worth a read. I think whatever we end up implementing > in Bigtop needs to be aligned (to the best possible extent) with Linux > vendors: > http://duncan.mac-vicar.com/2012/01/26/on-java-maven-jpp-and-rpm/ > http://fedoraproject.org/wiki/Packaging:Java#build-classpath > > Of course, if anybody has any concrete proposal I'd love for them to > be articulated on the JIRA or mailing list -- do let me know!
Thanks for the pointers Roman. Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
