On Wed, 8 Aug 2001 06:30, Berin Loritsch wrote:
> I would like to merge cadastre into Excalibur, and make the package
> named:
>
> org.apache.avalon.excalibur.naming
>
> As there is little confusion for Java developers as to what that means,
> and it follows the patterns set up for the Excalibur package as a whole.
I don't mind the rename ... though give me a bit so I can update all my
code ;)
However I do have a problem with the length of import statements. A direct
convertion will mean the length of our import statements are pushing 60
characters !!!! Not sure how to deal with this just yet thouygh ;)
> I think we need to only deal with Realy Cool Names (RCN) when there is
> a new project to be had.
I am not sure I agree with that ... it works when there is one instance of
component but fails when you get duplicates. Currently I have two other
packages in excalibur package waiting for me to actually commit them or throw
them out. One is a pool but different from our current version (an object
pool rather than component pool). Another is a simplified CLI parser ...
consequently they have the odd names excalibur.opool for object pool (thought
about opul or opal) and xcli for extended CLI services (when in reality it is
a simplified CLI ;]).
I guess in most cases I like simple names ... not sure. I think we should at
least be open to different ways.
> I don't think that Cadastre qualifies as it's
> own project, and it folds nicely into Excalibur's goal.
agreed.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
