Return-Path: Delivered-To: apmail-incubator-gora-dev-archive@minotaur.apache.org Received: (qmail 75667 invoked from network); 12 Mar 2011 17:45:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Mar 2011 17:45:49 -0000 Received: (qmail 592 invoked by uid 500); 12 Mar 2011 17:45:49 -0000 Delivered-To: apmail-incubator-gora-dev-archive@incubator.apache.org Received: (qmail 566 invoked by uid 500); 12 Mar 2011 17:45:49 -0000 Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: gora-dev@incubator.apache.org Delivered-To: mailing list gora-dev@incubator.apache.org Received: (qmail 558 invoked by uid 99); 12 Mar 2011 17:45:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Mar 2011 17:45:49 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of henry.saputra@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 Mar 2011 17:45:45 +0000 Received: by bwz10 with SMTP id 10so3255395bwz.6 for ; Sat, 12 Mar 2011 09:45:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=MdN/8s3ie3JKEAiJEsbGqSDd3yB/2Aq6pXYZbVvP+l8=; b=JrV1Bv0FOAjtTIgpfLvRAl7B5hh64JunBOlK3YaV5JSCebLAiqm6GpHiPLJ4HJXppT hKLjVqWyeI1DGwS0D6naihUWKf5oKd2Fas2idvdldPk7ee9AOX7hU9tugjrR4NBYhc05 MXHWLE7klbUg+V4LVe1ZsaUaM3luSnil/WVB8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Edk0oJWigzdFz1sUgfz0ytGzjTbNO/Y30K2E3ISzDZznVlVYNCVIoap2sy7GtqSxX2 UseQeVcZf+x+kCAo8NftOPYA5GGQAwqFOrGTJJ1jTACb+rxyjCHTnEhLXnFk1Dv2QLPW 1tuwWdpzZ3cg4uiAxuiD/C1REFg7F/zTxfM78= MIME-Version: 1.0 Received: by 10.204.7.17 with SMTP id b17mr9124442bkb.214.1299951923701; Sat, 12 Mar 2011 09:45:23 -0800 (PST) Received: by 10.204.17.9 with HTTP; Sat, 12 Mar 2011 09:45:23 -0800 (PST) In-Reply-To: References: Date: Sat, 12 Mar 2011 09:45:23 -0800 Message-ID: Subject: Re: Moving Gora build system to Maven? From: Henry Saputra To: gora-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hey Julien, I am trying to find if any of existing ASF projects has dual build systems. Want to see if this somewhat a "norm" for Apache projects. I agree its a bit pain maintaining two different systems (I did it at work and its not pretty). I also more happy to add more tests and support for features so using Ivy+ ANT is not a big deal for me =3D) My +1 is if we want to add Maven support, might as well make it parallel with existing Ivy+Ant. BTW, dont forget to VOTE on the RC3 thread ^_^ - Henry On Sat, Mar 12, 2011 at 3:23 AM, Julien Nioche wrote: > I am not particularly keen to have to maintain 2 systems in parallel, som= e > of you are maybe more familiar with Maven but as Chris pointed out most o= f > the Gora devs prefer ANT+Ivy and as far as I know the latter does not > prevent us from doing what we need i.e build, manage dependencies and > publish artifacts. Of course if this makes you happy, this is fine by me > but =C2=A0I'd rather we spent more effort on writing tests, add new > functionalities or improve the documentation instead of arguing which of = Ivy > or Maven is better. > > On 11 March 2011 21:55, Henry Saputra wrote: > >> +1 for this approach >> >> - Henry >> >> On Fri, Mar 11, 2011 at 1:52 PM, Mattmann, Chris A (388J) >> wrote: >> > Hi Ioannis, thank you very much! I am certainly more familiar with Mav= en >> then Ivy, and would be willing to help get these committed. >> > >> > I don't think parallel build systems hurt either. Most of the Gora dev= s >> though, realize, are Ant+Ivy users, so they will be more familiar with t= hat >> system. But, if we have Maven poms, those can be maintained as well. >> > >> > Thanks! I'll take a look at these. >> > >> > Cheers, >> > Chris >> > >> > On Mar 11, 2011, at 1:49 PM, Ioannis Canellos wrote: >> > >> >> I created issue https://issues.apache.org/jira/browse/GORA-29 and >> attached a >> >> patch which adds maven support to Gora. >> >> >> >> >> >> On Fri, Mar 11, 2011 at 12:12 PM, Ioannis Canellos > >wrote: >> >> >> >>> Hi all, >> >>> >> >>> I would prefer to see Gora use maven, for the following reasons: >> >>> >> >>> =C2=A0 - Maven promotes convention over configuration and re-usabili= ty >> (really >> >>> =C2=A0 important as the project grows, as it decreases the managemen= t >> overhead and >> >>> =C2=A0 ensures uniformity). >> >>> =C2=A0 - A Maven project is a lot easier to be imported to any IDE (= will >> make >> >>> =C2=A0 it easier for new Gora users. Now a lot of things need to be = done by >> >>> =C2=A0 "hand"). >> >>> =C2=A0 - Access to a wide plugin list that among others help release >> >>> =C2=A0 management, repository management. >> >>> =C2=A0 - Better support for tools like findbugs, pmd, colver and oth= er that >> >>> =C2=A0 can also be quite easily integrate with hudson / jenkins. >> >>> =C2=A0 - Better support for artifacts with classifier (I couldn't fi= nd to >> use >> >>> =C2=A0 classifier in dependencies with ivy). >> >>> >> >>> If the above are not enough to convince you, then you might want >> consider >> >>> the possibility of supporting both ant/ivy & maven builds. I would b= e >> more >> >>> that happy to contribute & maintain the maven project filles. >> >>> >> >>> >> >>> On Sun, Feb 6, 2011 at 2:20 PM, Julien Nioche < >> >>> lists.digitalpebble@gmail.com> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> Personally I'd rather stick to ant+ivy. Maybe you could reuse code >> from >> >>>> NUTCH-825 to >> publish >> >>>> using >> >>>> ant? >> >>>> Since most if not all current Gora users use it for Nutch 2.0, I th= ink >> it >> >>>> would make sense to keep the same ant+ivy mechanism >> >>>> >> >>>> Julien >> >>>> >> >>>> On 6 February 2011 09:16, Henry Saputra >> wrote: >> >>>> >> >>>>> HI Enis, >> >>>>> >> >>>>> The Maven release management plugin >> >>>>> (http://maven.apache.org/plugins/maven-release-plugin/) is probabl= y >> >>>>> the main reason why I was proposing to use Maven. >> >>>>> Having some targets to help doing this should do for now. >> >>>>> >> >>>>> I was just thinking about maven just because I use it more often t= han >> >>>>> ant+ivy =3D) >> >>>>> >> >>>>> - Henry >> >>>>> >> >>>>> On Sun, Feb 6, 2011 at 12:47 AM, Enis S=C3=B6ztutar >> >>>> wrote: >> >>>>>> Personally I prefer ant+ivy over maven, since I do not like anyth= ing >> >>>>>> automagical happening in my code. >> >>>>>> >> >>>>>> Could you elaborate on what will be the benefits apart from pushi= ng >> to >> >>>>> maven >> >>>>>> repository. I believe there is an ivy target to do just that, wou= ld >> >>>> that >> >>>>> be >> >>>>>> enough? >> >>>>>> >> >>>>>> Enis >> >>>>>> >> >>>>>> On Sat, Feb 5, 2011 at 11:36 PM, Henry Saputra < >> >>>> henry.saputra@gmail.com >> >>>>>> wrote: >> >>>>>> >> >>>>>>> Hi Guys, >> >>>>>>> >> >>>>>>> Just a food for thought, any thought about moving the build syst= em >> to >> >>>>>>> maven? >> >>>>>>> >> >>>>>>> I think there are more projects in Apache is using Maven and a l= ot >> of >> >>>>>>> Maven plugins that could make deploying and managing Gora releas= es >> >>>>>>> better. >> >>>>>>> >> >>>>>>> Is there any possible complexity./ issue to move it from Ivy? >> >>>>>>> >> >>>>>>> -- >> >>>>>>> Thanks, >> >>>>>>> Henry >> >>>>>>> >> >>>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> -- >> >>>>> Thanks, >> >>>>> Henry >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> * >> >>>> *Open Source Solutions for Text Engineering >> >>>> >> >>>> http://digitalpebble.blogspot.com/ >> >>>> http://www.digitalpebble.com >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> *Ioannis Canellos* >> >>> * >> >>> http://iocanel.blogspot.com >> >>> >> >>> Apache Karaf Committer & PMC >> >>> Apache ServiceMix =C2=A0Committer >> >>> * >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> >> >> >> >> >> >> -- >> >> *Ioannis Canellos* >> >> * >> >> http://iocanel.blogspot.com >> >> >> >> Apache Karaf Committer & PMC >> >> Apache ServiceMix =C2=A0Committer >> >> * >> > >> > >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > Chris Mattmann, Ph.D. >> > Senior Computer Scientist >> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> > Office: 171-266B, Mailstop: 171-246 >> > Email: chris.a.mattmann@nasa.gov >> > WWW: =C2=A0 http://sunset.usc.edu/~mattmann/ >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > Adjunct Assistant Professor, Computer Science Department >> > University of Southern California, Los Angeles, CA 90089 USA >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> > >> > >> >> >> >> -- >> Thanks, >> Henry >> > > > > -- > * > *Open Source Solutions for Text Engineering > > http://digitalpebble.blogspot.com/ > http://www.digitalpebble.com > --=20 Thanks, Henry