Path: csiph.com!eeepc.pasdenom.info!news.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!74.125.46.80.MISMATCH!postnews.google.com!8g2000prt.googlegroups.com!not-for-mail From: Joshua Maurice Newsgroups: comp.lang.java.programmer Subject: Re: Dependency resolution in Java builds Date: Wed, 9 Feb 2011 15:03:16 -0800 (PST) Organization: http://groups.google.com Lines: 31 Message-ID: <8ee0386d-478d-4ef0-8b9d-41e9592bb2f3@8g2000prt.googlegroups.com> References: <87oc6mi2nl.fsf@web.de> <87aai5k75w.fsf@web.de> NNTP-Posting-Host: 12.108.188.134 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1297292596 23457 127.0.0.1 (9 Feb 2011 23:03:16 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 9 Feb 2011 23:03:16 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: 8g2000prt.googlegroups.com; posting-host=12.108.188.134; posting-account=C7XBLgoAAAAxMpmeFo8Iv_pud1pyFhjy User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Xref: csiph.com comp.lang.java.programmer:26012 On Feb 9, 5:11=A0am, Lew wrote: > Markus Gessner wrote: > > It is a host of pom.xml-files, so this would not be feasible, but I > > greatly appreciate your kind offer! > > The highly-touted features of Maven, namely the auto-resolution of > dependencies across the Internet, are confusing enough. =A0Add the pom.xm= l > spaghetti perpetrated by the same numb-nuts who write spaghetti code and = your > situation gets pathetic indeed. > > I'm on a project now with Maven builds that we inherited from such > incompetents. =A0I've been part of an effort that's so far taken eight mo= nths to > resolve the build issues. =A0It's a combination of bad project organizati= on and > Maven abuse (with a liberal dose of framework [Spring, et al.] abuse). = =A0The > trouble is you change something in one module (with its own pom.xml) and = it > breaks something in another related module. =A0And that one only had ten > pom.xmls at its peak, down to seven thanks to our efforts. I've been experiencing Maven hell for a couple years now. I think we're over 1000 poms in a build which developers are expected to do before each checkin. The automated build machine does that 1000 pom build daily (or more) as well. Maven is the main driver of the build. The build includes Java, C++, various in-house code generators, /and/ some Eclipse plugin build stuff which is cobbled together with some rather poor scripts. Feel my pain.