From ant-dev-return-29500-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Mon Apr 08 10:07:55 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 97355 invoked from network); 8 Apr 2002 10:07:53 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Apr 2002 10:07:53 -0000 Received: (qmail 8272 invoked by uid 97); 8 Apr 2002 10:07:59 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 8193 invoked by uid 97); 8 Apr 2002 10:07:58 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 8035 invoked from network); 8 Apr 2002 10:07:58 -0000 Content-Type: text/plain; charset="utf-8" From: Adam Murdoch To: "Ant Developers List" Subject: Re: [myrmidon] moving to new module Date: Mon, 8 Apr 2002 20:10:53 +1000 X-Mailer: KMail [version 1.4] References: <200204081849.52691.adammurdoch@apache.org> <200204080858.g388wKl09080@mail017.syd.optusnet.com.au> In-Reply-To: <200204080858.g388wKl09080@mail017.syd.optusnet.com.au> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200204082010.53363.adammurdoch@apache.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 8 Apr 2002 18:54, Peter Donald wrote: > On Mon, 8 Apr 2002 18:49, Adam Murdoch wrote: > > What's the plan for moving myrmidon to the new cvs module? > > I was going to do it as soon as possible after the excalibur CVS settle= s > down in build structure and chooses a build system (be it XSLT, maven, > forrest or whatever).=20 I wonder if it's time to start building myrmidon using myrmidon? The pro= ject=20 descriptor + transforming project builder approach would be interesting t= o=20 try. Definitely the way of the future. The question is, which descripto= r to=20 use? Regardless, we don't really need to wait for excalibur to get sorted out.= For=20 the time being we can go with the uber-script we have now. We just have = to=20 schlurp over more directories. > However if you want it to move faster then we can do > it now. Up to you. Let's get the structure sorted out, at the very least. As I understand i= t,=20 the current plan is to split the tree up into something like: - AUT, o.a.aut.* - Task API, o.a.myrmidon.api.* and probably a few bits and pieces from=20 o.a.myrmidon.framework.*. - Container API, o.a.myrmidon.interfaces.* - Container impl, o.a.myrmidon.components.* - Antlibs, o.a.antlib.* - Framework, o.a.myrmidon.framework.* - Ant1compat, o.a.tools.ant.* - Todo, o.a.tools.todo.* These last 4 are all kinda the same. Probably want to rearrange 'em into= 3=20 broad groups: - general stuff that ends up in the shared classloader (most of what's in= =20 framework and some of todo). - reusable stuff that ends up in non-final antlibs (ant1 compat, bits fro= m the=20 others). - private stuff that ends up in final antlibs (the rest). Not entirely sure how to tackle these. We could move 'em all under=20 o.a.antlib.*, I suppose (except the ant1 compat stuff, of course). The other question is package names. Do we want to move the task API out= of=20 o.a.myrmidon? The container api and impl are probably fine where they ar= e. --=20 Adam -- To unsubscribe, e-mail: For additional commands, e-mail: