You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Jörg Henne <j....@levigo.de> on 2007/12/19 14:04:12 UTC

Technicalities of migration of LDAP mapping component to Apache DS project

Hi all,

donating the openthinclient.org LDAP mapping component to the Apache DS 
project raises the question of how other members of the 
openthinclient.org team work on the source code. There are currently two 
colleagues of mine working on the code. I see the following solutions:

- We maintain two completely separate code bases. That doesn't sound 
desirable, since they will diverge quickly.
- We maintain the code in the Apache svn. This would require commit 
access for the code tree of the mapping component.
- We maintain the code in the openthinclient.org svn under a tree 
separate from our main code base. We can easily add other committers 
there, but I don't know whether this is ok with you.

WDYT?

Oh, and by the way: does anyone can think of a catchy name for this 
thing? It doesn't have to be creative or clever but only a tad bit less 
boring than Object Directory Mapper (ODM?). Currently it doesn't have a 
name at all :-)

Joerg Henne


Re: Technicalities of migration of LDAP mapping component to Apache DS project

Posted by Alex Karasulu <ak...@apache.org>.
No worries and I'll make sure to checkout from 'common'.  Thanks for the
heads up.

Alex

On Dec 19, 2007 2:02 PM, Jörg Henne <j....@levigo.de> wrote:

> Alex,
>
> Alex Karasulu schrieb:
> > OK thanks Jorg I'll take a look tonight.
> if you want to take a deeper look you can check out the 'common'
> subproject. Maven should pull all the dependencies from our repository.
> Please be aware that currently several test cases are broken, since we
> are in the process of tearing apart this subproject.
>
> Joerg Henne
>

Re: Technicalities of migration of LDAP mapping component to Apache DS project

Posted by Jörg Henne <j....@levigo.de>.
Alex,

Alex Karasulu schrieb:
> OK thanks Jorg I'll take a look tonight.
if you want to take a deeper look you can check out the 'common' 
subproject. Maven should pull all the dependencies from our repository. 
Please be aware that currently several test cases are broken, since we 
are in the process of tearing apart this subproject.

Joerg Henne

Re: Technicalities of migration of LDAP mapping component to Apache DS project

Posted by Alex Karasulu <ak...@apache.org>.
OK thanks Jorg I'll take a look tonight.

Alex

On Dec 19, 2007 12:00 PM, Jörg Henne <j....@levigo.de> wrote:

> Alex Karasulu schrieb:
> > Hi,
> >
> > We need to evaluate the size of the contribution.  Jorg can you point
> > us over to the code repository for it?
> not too large I'd, say. I haven't completely factored out the stuff, but
> I guess it will be roughly 25 classes with the bulk of the core
> currently living here:
>
> http://openthinclient.svn.sourceforge.net/svnroot/openthinclient/suite/trunk/common/src/main/java/org/openthinclient/ldap/
>
> Joerg Henne
>
>
>

Re: Technicalities of migration of LDAP mapping component to Apache DS project

Posted by Jörg Henne <j....@levigo.de>.
Alex Karasulu schrieb:
> Hi,
>
> We need to evaluate the size of the contribution.  Jorg can you point 
> us over to the code repository for it? 
not too large I'd, say. I haven't completely factored out the stuff, but 
I guess it will be roughly 25 classes with the bulk of the core 
currently living here: 
http://openthinclient.svn.sourceforge.net/svnroot/openthinclient/suite/trunk/common/src/main/java/org/openthinclient/ldap/

Joerg Henne



Re: Technicalities of migration of LDAP mapping component to Apache DS project

Posted by Alex Karasulu <ak...@apache.org>.
Hi,

We need to evaluate the size of the contribution.  Jorg can you point us
over to the code repository for it?

On Dec 19, 2007 8:04 AM, Jörg Henne <j....@levigo.de> wrote:

> Hi all,
>
> donating the openthinclient.org LDAP mapping component to the Apache DS
> project raises the question of how other members of the
> openthinclient.org team work on the source code. There are currently two
> colleagues of mine working on the code. I see the following solutions:
>
> - We maintain two completely separate code bases. That doesn't sound
> desirable, since they will diverge quickly.
> - We maintain the code in the Apache svn. This would require commit
> access for the code tree of the mapping component.


We can easily accommodate this at some point considering the different
mechanisms available for bringing in new subprojects.  The Directory PMC has
to evaluate how to process this: i.e. does this need incubation or is it
small enough to constitute a simple contribution.


>
> Oh, and by the way: does anyone can think of a catchy name for this
> thing? It doesn't have to be creative or clever but only a tad bit less
> boring than Object Directory Mapper (ODM?). Currently it doesn't have a
> name at all :-)
>

ODM sounds good.  I suck at names but I'll let it sit in my head to see if
any ideas come to mind.

Alex