Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 60384 invoked from network); 5 Mar 2004 19:24:51 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 19:24:51 -0000 Received: (qmail 62407 invoked by uid 500); 5 Mar 2004 19:24:39 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 62348 invoked by uid 500); 5 Mar 2004 19:24:38 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 62335 invoked from network); 5 Mar 2004 19:24:38 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by daedalus.apache.org with SMTP; 5 Mar 2004 19:24:38 -0000 Received: from comcast.net (h-68-164-32-243.nycmny83.covad.net[68.164.32.243]) by comcast.net (sccrmhc12) with ESMTP id <2004030519244201200t01bre> (Authid: hkrishnaswamy); Fri, 5 Mar 2004 19:24:42 +0000 Message-ID: <4048D3FD.5040109@comcast.net> Date: Fri, 05 Mar 2004 14:24:45 -0500 From: Harish Krishnaswamy User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [HiveMind] multi-module classloader References: <4047477F.9040800@streber24.de> In-Reply-To: <4047477F.9040800@streber24.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I like the idea although another xml file to maintain. But it could be a hivemeta file that can store all the meta information. -Harish achim@streber24.de wrote: > > I just wanted to post this in case anyone else was interested and to > draw any > > criticism about how this could mess something > > up or trigger armageddon. It allows a list of hivemodule.xml > locations to be defined > > in a .property file. > > I reason I wanted this was because I really wanted to split up the > descriptors but > > still wanted all the code in the same > > Eclipse project. > > Hi, > > I see the need for such a list of modules too. I would suggest to use > xml as file format (it can't be > denied that hivemind is xml centric). Such a 'directory' file could > look like this: > > > > > > > This could be the same file format that is used for 'breaking the one > jar == one module" approach, like Howard put it in this posting: > http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg37000.html > > Such a directory could be found by file naming conventions > (META-INF/hivedir.xml) or it could be referenced from a manifest file. > > Bye > Achim > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org