[EMAIL PROTECTED] writes:
>However, that may be the easiest approach to take in the short term.
>Where you thinking that people would have a single file with two namespaces
>in it, one for the meta configuration inforamtion, and one for the turbine
>(old TR.props) stuff?
>Also, I think having it be it's own file isn't horrible, because it appears
>that the avalon components will be configed in their own files as well?
I don't like an inflation of lots of small configuration files. In the end
you will get confused where to configure what.
I'd propose that you go on and put your turbine-related stuff into the
proposals/ directory so we can check out and let it incubate there
until it is stable. Then we can move it in.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
