From easyant-dev-return-230-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Tue Nov 22 08:57:00 2011 Return-Path: X-Original-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C4CE99676 for ; Tue, 22 Nov 2011 08:57:00 +0000 (UTC) Received: (qmail 67786 invoked by uid 500); 22 Nov 2011 08:57:00 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 67762 invoked by uid 500); 22 Nov 2011 08:57:00 -0000 Mailing-List: contact easyant-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: easyant-dev@incubator.apache.org Delivered-To: mailing list easyant-dev@incubator.apache.org Received: (qmail 67754 invoked by uid 99); 22 Nov 2011 08:56:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Nov 2011 08:56:59 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted sender) Received: from [216.86.168.183] (HELO mxout-08.mxes.net) (216.86.168.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Nov 2011 08:56:53 +0000 Received: from [10.0.0.238] (unknown [92.103.90.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 51926509DB for ; Tue, 22 Nov 2011 03:56:31 -0500 (EST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Easyant bootstrap doesn't build From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= In-Reply-To: <0818BFC9-23EB-494E-A5E6-07FA56311103@hibnet.org> Date: Tue, 22 Nov 2011 09:56:29 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <660052C7-5641-48FD-9998-F4B955E5E0B2@hibnet.org> References: <7C21F8E8-DFBE-479B-8A81-91B1A20C7F53@hibnet.org> <0818BFC9-23EB-494E-A5E6-07FA56311103@hibnet.org> To: easyant-dev@incubator.apache.org X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org Le 12 nov. 2011 =E0 15:36, Nicolas Lalev=E9e a =E9crit : > I have fixed the bootstrap build. Unless somebody objects, I'll setup = a build job on the Jenkins hosted at the ASF and get build failure sent = to easyant-notification@. done. https://builds.apache.org/job/EasyAnt/ Nicolas >=20 > So for the bootstrap build, there is a specific ivysettings because we = need to compute a classpath to compile and just that. We cannot have an = ivysettings which is referencing some repository in easyant's classpath, = since easyant isn't yet build. Once compiled and jared, easyant is = launched and then the ivysettings used is the nominal one. Note that = there is an ivysettings-bootstrap.xml just because we're using Ivy = trunk. Once Ivy 2.3 will be released, it could just rely on Ivy's = default settings which is just referencing maven central. >=20 > Nicolas >=20 > Le 27 sept. 2011 =E0 11:49, Jean-Louis Boudart a =E9crit : >=20 >> Hum good catch, commons-cli was retrieved from my cache. >>=20 >> This raise the question : Should we have two different ivysettings, = one for >> easyant boostrap / build, and a second one shipped in easyant = distribution >> and used end user ? >>=20 >> Supposing we have the following chain of resollution in = ivysettings.xml : >>=20 >> - a localrepository (~/.easyant/repository by default) >> - an embedded resolver (using the new implementation of jar = resolver) >> - an online repository accessible through http accessible at >> repository.easyant.org >> - an http resolver using maven central repository (if we decide to = not >> use repository.easyant.org as a proxy of other online maven = repository) >>=20 >> We'll probably use artifactory as a repository manager on >> repository.easyant.org to host all our stuff (plugins, buildtypes, = tasks, >> skeletons). Artifactory can acts as a proxy of other online = repository see >> = http://wiki.jfrog.org/confluence/display/RTF/Understanding+Repositories = for >> further details. >>=20 >> Here is how i imagine things : >>=20 >> - Plugins, buildtypes, and additionnal tasks are published on >> repository.easyant.org. This includes both Apache and non Apache = plugins >> (i guess those not compatible with Apache policy such as checkstyle, = sonar >> etc....) >> - Easyant is built with easyant. When building easyant itself we use = the >> *same* ivysettings as the one used by default by end users (the one >> described above). >> - Nothing will be found in local repository >> - embedded resolver will probably be empty as were in bootstrap = mode >> - it will fetch plugins from our online repository >> repository.easyant.org >> - How could we build the embedded repository ? We will probably ship = one >> or many version of "core plugins" in easyant distribution as plugins = can be >> updated but still be compatible with easyant-core. How could we = maintain >> this ? >> - We could use ant task to copy explicit version of = core >> plugins from our official repository (repository.easyant.org) to = a >> filesystem structure that will be shipped in the jar. This can >> be done as >> an intial step when creating easyant distribution. >>=20 >> If we use this flow we could use the same ivysettings as the one = shipped by >> default in easyant distribution and leverage maintenance of this = file. >>=20 >> Any feedback would be really appreciated. >>=20 >>=20 >> Le 26 septembre 2011 10:12, Nicolas Lalev=E9e = a >> =E9crit : >>=20 >>>=20 >>> Le 25 sept. 2011 =E0 22:41, Jean-Louis Boudart a =E9crit : >>>=20 >>>> On my computer, commons-cli is retrived from maven central repo. = When you >>>> tried the bootstrap build did you have access to internet ? >>>=20 >>> In the bootstrap build (with ant, with the build.xml), it is hard = coded to >>> use repository/third-party-lib/third-party-ivysettings.xml. And it = doesn't >>> reference maven. So I guess it is wrong ? >>>=20 >>> Nicolas >>>=20 >>>=20 >>=20 >>=20 >> --=20 >> Jean Louis Boudart >> Independent consultant >> Apache EasyAnt commiter http://incubator.apache.org/easyant/ >=20