Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates
 209.85.161.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:date:from:to:message-id:in-reply-to:references:subject
         :x-mailer:mime-version:content-type:content-transfer-encoding;
        b=AOYfjArawttSNOmcIBP8oP13z64qdx8SnmncbShMbF+Voe78F8s32qf+Plgw2ZZRXk
         PFf03w6BrzLd+7pbm0bpdC1IavezhTluyAUspjAecDBM8qdnDrZv8KgKRz//UjoRnZ11
         BJ9/VEm+Wpzh1wDXwhEZeHpyfqwfviXqvRjMI=
Sender: Pierre-Arnaud Marcelot <pajbam@gmail.com>
Date: Mon, 28 Feb 2011 13:30:46 +0100
From: Pierre-Arnaud Marcelot <pa@marcelot.net>
To: Apache Directory Developers List <dev@directory.apache.org>
Message-ID: <86E176AE01E9435CA1290E80C5A47E8E@gmail.com>
In-Reply-To: <AANLkTinf8rmGyCB+=-cid3MWoCFUVSBeJO5=TiYG=4GQ@mail.gmail.com>
References: <AANLkTinf8rmGyCB+=-cid3MWoCFUVSBeJO5=TiYG=4GQ@mail.gmail.com>
Subject: Re: [Shared] [SCM] Thinking about some hierarchy in shared.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4d6b9576_26f2d364_3832"
Content-Transfer-Encoding: 8bit

--4d6b9576_26f2d364_3832
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline

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
> 

--4d6b9576_26f2d364_3832
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>
            <div><span>Hi Alex,</span></div><div><span><br></span></div><=
div><span>Very good idea.</span></div><div><span>I like this reorganizati=
on a lot.</span></div><div><span><br></span></div><div><span>At some poin=
t with our number of projects increasing, it really makes sense to group =
them in some kind of logical organization.</span></div><div><span>We did =
the same thing for Studio a few months ago.</span></div><div><span><br></=
span></div><div><span>+1&nbsp;<br>
                </span>
                <span><br><div>Regards,<br>Pierre-Arnaud</div><br></span>=

               =20
                <p style=3D=22color: =23a0a0a0;=22>On lundi 28 f=C3=A9vri=
er 2011 at 04:50, Alex Karasulu wrote:</p>
                <blockquote type=3D=22cite=22 style=3D=22border-left-styl=
e:solid;border-width:1px;margin-left:0px;padding-left:10px;=22>
                    <span><div><div>Hi all,<br><br>Shared has grown somew=
hat and I think it will grow more as we tack on<br>more protocol addition=
s and functionality. I was thinking of using<br>some project module hiera=
rchy to try to establish some organization we<br>can grow with.<br><br>He=
re's what I was thinking:<br><br>shared/<br>    i18n/<br>    util/<br>   =
integ/<br>    asn1/<br>        api/<br>        ber/<br>    dsml/<br>     =
   parser/<br>        engine/<br>    ldap/<br>        codec/<br>        m=
model/<br>        schema/<br>        schema-converter/<br>        client-=
api/<br>        codec-standalone/<br>        all/<br>        protocol/<br=
>            mina/<br>        extras/<br>            aci/<br>            =
sp/<br>            trigger/<br>            util/<br>            archetype=
/<br>               control/<br>               extended/<br>             =
 schema/<br>            codec/<br>               api/<br>               p=
plugin/<br><br>The deepest level is 5 and we'd concat levels into the nam=
es as we<br>kind of do already. Here is the very last node,<br>shared-lda=
p-extras-codec-plugin, as an example of the artifactId<br>composition sta=
ndard.<br><br>Thoughts=3F<br><br>Thanks,<br>Alex<br></div></div></span>
               =20
               =20
               =20
               =20
                </blockquote>
               =20
                <div>
                    <br>
                </div>
            </div>
        </div>
--4d6b9576_26f2d364_3832--