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

Reply via email to