I remember the old days of ivy builds in hadoop... Ivy configuration is large and I thought it was messy - duplication of values a lot. Maybe it might have been to not following best practices, but that doesnt really diminish the fact. Configuring the maven-compatible artifacts seemed to use a lot of build.xml, and it was entirely up to the developer to define commands to install packages in ~/.m2, which meant that you may end up copying jars.
Pure ant == jars in your repo, which I think we can agree isn't acceptable. As for maven, well the build is encapsulated in 1 file, it really isn't that bad if your project is a 'normal' java project for example, and figuring out problems in maven is very 'googleable'. Which is more than I can say for sbt. Usually 1 person sets it up, and the only thing people do is add new dependencies, which is pretty trivial - yeah it's XML but get over it. I hardly love XML, but I love these things more: - integration with every single build tool on the planet - full, and deep integration with intellij, The Best IDE On The Planet... - I hear eclipse can handle maven, but I wouldnt know... :-) - plugins for nearly every single Java and Scala tasks *ever*. Now maven is a Java build tool, it can "build" C++, but by shelling out to Make or Jam or shell scripts or anything. It doesnt really manage the C++ build, but the way I've seen things work is top level with maven, and calling C++ as a sub-task. Or vice versa really, it doesn't matter. I personally like how it integrates with IDEs - you point your IntelliJ at a pom.xml and bam, you have a fully working, BUILDING project. No fuss, no muss, and new developers can start to write (Java) code immediately and running tests. I've tried the IntellijJ,SBT integration and it was lacking. It might be better now, but after the multiple flag days. If you must use !maven, at least use gradle - which also has intellij integration. Really, if I can convey any message it's the build system should interoperate with intellij/eclipse for Java code. -ryan On Fri, Sep 14, 2012 at 10:17 PM, Jim Donofrio <[email protected]> wrote: > Definite +1 for maven over Ant. I can help with Maven. > > > On 09/12/2012 05:39 PM, Ted Dunning wrote: >> >> On a large hierarchical project, Ant becomes hopeless (see Hadoop). >> >> Maven is quite tolerable if you have somebody who does it for you. >> >> You have somebody (me if nobody else, but there have been other volunteers >> as well). >> >> On Wed, Sep 12, 2012 at 1:53 PM, Vladimir Klimontovich < >> [email protected]> wrote: >> >>> I guess ant is good too if it's used together with ivy. >>> >>> >>> On Thu, Sep 13, 2012 at 12:51 AM, Camuel Gilyadov <[email protected]> >>> wrote: >>>> >>>> What is wrong with good old Ant? >>>> I can live with maven too... it just has too many gotchas >>>> >>>> On 9/12/12, Julien Le Dem <[email protected]> wrote: >>>>> >>>>> +1 for maven. >>>>> Could those against please suggest alternatives? >>>>> Thank you >>>>> Julien >>>>> >>>>> On Wed, Sep 12, 2012 at 1:32 PM, Camuel Gilyadov <[email protected]> >>> >>> wrote: >>>>>> >>>>>> -1 for maven. >>>>>> >>>>>> On 9/12/12, Constantine Peresypkin <[email protected]> wrote: >>>>>>> >>>>>>> If build system is evil it's better to build it manually. >>>>>>> -1 for maven >>>>>>> >>>>>>> On Wed, Sep 12, 2012 at 9:53 PM, Michael Hausenblas < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>>> I know that no-one has mentioned this before but what about the >>>>>>>>> build >>>>>>>> >>>>>>>> system for drill? >>>>>>>>> >>>>>>>>> I'm personally in favor of maven (lesser evil for java IMO). >>>>>>>>> I'd be happy to contribute that setup, if needed. >>>>>>>> >>>>>>>> If codebase mainly in Java, yeah maven (though it feels like it >>>>>> >>>>>> downloads >>>>>>>> >>>>>>>> half of the Internet every time). >>>>>>>> >>>>>>>> But not so fast - did we agree on Java, yet? How about Scala + SBT >>>>>>>> [1]? >>>>>>>> Integrates nicely with Java and is soooo much more productive ;) >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Michael >>>>>>>> >>>>>>>> [1] http://www.scala-sbt.org/ >>>>>>>> >>>>>>>> -- >>>>>>>> Michael Hausenblas >>>>>>>> Ireland, Europe >>>>>>>> http://mhausenblas.info/ >>>>>>>> >>>>>>>> On 12 Sep 2012, at 20:47, David Alves wrote: >>>>>>>> >>>>>>>>> I know that no-one has mentioned this before but what about the >>>>>>>>> build >>>>>>>> >>>>>>>> system for drill? >>>>>>>>> >>>>>>>>> I'm personally in favor of maven (lesser evil for java IMO). >>>>>>>>> I'd be happy to contribute that setup, if needed. >>>>>>>>> >>>>>>>>> -david >>>>>>>>> >>>>>>>>> On Sep 12, 2012, at 1:42 PM, Ted Dunning <[email protected]> >>>>>> >>>>>> wrote: >>>>>>>>>> >>>>>>>>>> I see classes in the source tree: >>>>>>>>>> >>>>>>>>>> >>> >>> https://github.com/ApacheDrill/parser/tree/master/src/org/apache/drill/parsers/impl/drqlantlr/autogen/classes/org/apache/drill/parsers/impl/drqlantlr/autogen >>>>>>>>>> >>>>>>>>>> Also, I would strongly recommend pulling the antlr source code >>> >>> into >>>>>> >>>>>> an >>>>>>>>>> >>>>>>>>>> antler source tree. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Sep 12, 2012 at 11:31 AM, Camuel Gilyadov >>>>>>>>>> <[email protected]>wrote: >>>>>>>>>> >>>>>>>>>>> Still work in progress, but anyway - >>>>>>>> >>>>>>>> https://github.com/ApacheDrill/parser >>>>>>>>>>> >>>>>>>>>>> Constructive critique and contributions are welcome >>>>>>>>>>> >>>>>>>> >>>>>> -- >>>>>> Sent from my mobile device >>>>>> >>>> -- >>>> Sent from my mobile device >>> >>> >>> >>> -- >>> Vladimir Klimontovich >>> Cell: +7-926-890-2349, skype: klimontovich >>> >
