Apache Directory Project - Forking rules

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > October 2005 > Forking rules





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Forking rules
Trustin Lee

2005-10-25, 7:45 am

Hi,

It would be great if we have some general rule of where to place forked
classes.

What I suggest is just copying the whole classes to
org.apache.ldap.support.fork.<original package name>. (e.g.
oeg.apache.ldap.support.fork.org.apache.commons.collections)

For now it is not really easy to manage forked classes. So I think just
copying the whole classes is the best way we can minimize management
overhead.

WDYT?

Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/

Alex Karasulu

2005-10-25, 5:45 pm

Trustin Lee wrote:

> Hi,
>
> It would be great if we have some general rule of where to place
> forked classes.
>
> What I suggest is just copying the whole classes to
> org.apache.ldap.support.fork.<original package name>. (e.g.
> oeg.apache.ldap.support.fork.org.apache.commons.collections )
>
> For now it is not really easy to manage forked classes. So I think
> just copying the whole classes is the best way we can minimize
> management overhead.
>
> WDYT?


Not a bad idea. Then copying forked stuff is much easier. But if we go
this route someone should move the classes we already forked into this
package configuration. Let's not do it unless already forked classes
are also moved.

Alex


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com