directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot ...@marcelot.net>
Subject Re: [Shared] [SCM] Thinking about some hierarchy in shared.
Date Mon, 28 Feb 2011 12:30:46 GMT
Hi Alex,

Very good idea.
I like this reorganization a lot.

At some point with our number of projects increasing, it really makes sense to group them
in some kind of logical organization.
We did the same thing for Studio a few months ago.

+1 

Regards,
Pierre-Arnaud
On lundi 28 février 2011 at 04:50, Alex Karasulu wrote: 
> Hi all,
> 
> Shared has grown somewhat and I think it will grow more as we tack on
> more protocol additions and functionality. I was thinking of using
> some project module hierarchy to try to establish some organization we
> can grow with.
> 
> Here's what I was thinking:
> 
> shared/
>  i18n/
>  util/
>  integ/
>  asn1/
>  api/
>  ber/
>  dsml/
>  parser/
>  engine/
>  ldap/
>  codec/
>  model/
>  schema/
>  schema-converter/
>  client-api/
>  codec-standalone/
>  all/
>  protocol/
>  mina/
>  extras/
>  aci/
>  sp/
>  trigger/
>  util/
>  archetype/
>  control/
>  extended/
>  schema/
>  codec/
>  api/
>  plugin/
> 
> The deepest level is 5 and we'd concat levels into the names as we
> kind of do already. Here is the very last node,
> shared-ldap-extras-codec-plugin, as an example of the artifactId
> composition standard.
> 
> Thoughts?
> 
> Thanks,
> Alex
> 

Mime
View raw message