-Harish
Christian Essl wrote:
What's about loading all META-INF/hivemodule.xml files and everything contained in META-INF/hivedir.xml files. So you don't have to maintain hivedir.xml if you don't need it.
On Fri, 05 Mar 2004 14:24:45 -0500, Harish Krishnaswamy <[EMAIL PROTECTED]> wrote:
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
[EMAIL PROTECTED] 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:
<directory> <module fileName="testA/module1.xml" /> <module fileName="testB/module2.xml" /> </directory>
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/[EMAIL PROTECTED]/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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
