Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 82086 invoked from network); 10 Jan 2008 20:19:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jan 2008 20:19:22 -0000 Received: (qmail 74856 invoked by uid 500); 10 Jan 2008 20:19:11 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 74798 invoked by uid 500); 10 Jan 2008 20:19:11 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 74787 invoked by uid 99); 10 Jan 2008 20:19:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2008 12:19:11 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 72.14.252.153 as permitted sender) Received: from [72.14.252.153] (HELO po-out-1718.google.com) (72.14.252.153) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2008 20:18:45 +0000 Received: by po-out-1718.google.com with SMTP id c31so1434170poi.0 for ; Thu, 10 Jan 2008 12:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=yHQUWC4XxXpXBmKK7P590MHdM5F+W+ueDn/VORVvyuM=; b=URyYjI+N/TWVmw7hxI0zeRlRODxAdiO3ue68p3UhLkPSFAkXmI4y3EE0sKYm6NVJDafqgLCfYZ2I0KB53GUH259NsLg8gp9SEB7+CuH9eemb9WLiP4swZT8l+6BlwBbup4ucm0LxQH8citNhl5/HYlRiH/RaepW3YdfO1tMp04Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=FOc3OJdmX/6kfn+KFCH1XCdWatcN3IcZ3wXod+BZQtHqt5bsOjXF6QM3KXZhpvs6/Xw0mTbGEaSIEy5N3cOZTICs8TMnBevfGHnfUWezT42cCwr63+faib/VPYLOkm3u6YC23EmP/4sWbm+uTJ/0CtYK+QWMf06qlEYpe4xuBwg= Received: by 10.140.179.25 with SMTP id b25mr1479921rvf.152.1199996330417; Thu, 10 Jan 2008 12:18:50 -0800 (PST) Received: by 10.140.225.10 with HTTP; Thu, 10 Jan 2008 12:18:50 -0800 (PST) Message-ID: <635a05060801101218m5cfb5a6ft1f5297d455cbefd4@mail.gmail.com> Date: Thu, 10 Jan 2008 21:18:50 +0100 From: "Xavier Hanin" To: "Ant Developers List" Subject: Re: [DISCUSS] EasyAnt: Ant based pre packaged build system for java projects In-Reply-To: <14741437.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19634_4193283.1199996330395" References: <635a05060801100625n3e7a891bi69f7bca5d54ddb5f@mail.gmail.com> <255d8d690801100813l24d1d1efu84778037dd91c7cd@mail.gmail.com> <635a05060801100834gec2dfbfk2d65484a3447dcef@mail.gmail.com> <14741437.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_19634_4193283.1199996330395 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Jan 10, 2008 8:16 PM, kermitt wrote: > > I wish we could find a way to bundle common tasks : I have more than 9 > templates : > > build-common.xml > build-j2ee.xml > build-war.xml > build-ejb.xml > build-ws.xml > build-client-ws.xml > build-ear.xml > ... > > These builds just formalize my build system based on Ivy. > For each project I need to sync those files which is a pain within a team. > How to enforce team to use your build process, how do you easly patch, > add > feature. It's puzzling me. Today I need to copy paste all these files all > over my projects. > > I think Ivy dictate somehow the build process as you always need to > perform > some tasks configure/resolve/cachepath... > > My common-build.xml has 9 visible targets: > > all -> clean , build , package , publish > build -> init ivy -> resolve -> compute classpath -> do I have something > to > build ? (has dependencies changed? files ?) -> find what is the next > release -> compile > clean -> clean any generated files > doc -> build any doc > package -> make a jar > publish -> get current ivy version -> publish jar on local repo > share -> publish jar on integration repo > release -> publish jar in test/prod repo > test -> lauch unit tests > > > I wish Ant import would support URL + jar like that : > > > > > > As ivy became a sub project, it would make sense to have a closer > integration like : > > > > > > > we could imagine deeper integration : > > > ivyFile="${basedir]/ivy.xml"/> > > Improving the import mechanism to leverage Ivy is indeed a good idea and a good solution to package the build system parts. I also like what has been done in merevaik, leveraging directly the xmlns support in Ant (see the comment on my blog). Xavier > > > I think is not easy to not like maven ... but Xavier is right it's time to > go a step beyond with ant+ivy > > > So any comments on that ? > > > > > > > -- > View this message in context: > http://www.nabble.com/-DISCUSS--EasyAnt%3A-Ant-based-pre-packaged-build-system-for-java-projects-tp14735371p14741437.html > Sent from the Ant - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org > For additional commands, e-mail: dev-help@ant.apache.org > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_19634_4193283.1199996330395--