Le 7 juin 05, à 23:43, Sylvain Wallez a écrit :
> Daniel Fagerstrom wrote:
>> ...So IMO we need a policy for package naming. Is there any "style
>> guide" for package names for Eclipse plugins that we can adapt?
>> Otherwise using something like:
>>
>> org.apache.cocoon.blockname.**
>
>
> Yep. That's how it's done for Eclipse plugin. Each plugin has a name
> which is unique among all plugin and which is the root package for
> classes contained in the plugin...
Just thinking, because I'm working on a block:
org.apache.cocoon.blocks.blockname.**
might be better, the blocks prefix makes name clashes less probable.
-Bertrand
|