You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lecharny <el...@gmail.com> on 2006/10/27 08:09:11 UTC

MINA Trunks & ADS

Hi all,

we have to figure out a way to work with MINA as it will become soon a TLP.

Currently, ADS 1.0 use MINA 1.0, and it's working great, but we have had 
to wait for a 1.0 version of MINA to be able to release ADS 1.0.

For ADS trunks, wa are facing some problems : as the MINA API has 
changed, ADS is broken in trunks. A decision should be taken regarding 
this kind of problem, because we won't be able to cope with those kind 
of modifications when MINA will be a TLP.

I think that we should depend on a released version of MINA, not on MINA 
trunk, and manage the version through dependencies (thanks to maven, 
this is possible ;)

wdyt ?

Emmanuel

Re: MINA Trunks & ADS

Posted by Ersin Er <er...@gmail.com>.
Hi,

That was me who updated all package interdependencies in trunks so
that all projects depend on snapshot versions of each other. The
reason for doing that is making sure that the trunks is self-contained
so that it can be built without downloading any Directory packages
from remote repositories.

But of course this will change with MINA being a TLP. However, to be
able to depend on released versions of MINA in Directory trunks, MINA
should release more frequently. Because MINA 1.0 is _too old_ for
trunks now. And it's not possible to depend on any version of 1.1
branch (of MINA) because they are all 1.1-SNAPSHOT.. (I do not say
that there are problems with MINA versioning. I just say that it does
not fit perfectly.)

So what we can do is depend on MINA 1.0 in trunks and modify all the
code adapted to 1.1 or depend on beta/alpha releases of MINA 1.1. In
the first case ADS will depend on a relatively old version of the cool
MINA API. In the second case ADS we will always have a building trunks
and upgrade to new beta/alpha versions of MINA making sure that all
the trunks still compiles still.

Has it been a bit complicated? Sorry :)

Cheers,

On 10/27/06, Emmanuel Lecharny <el...@gmail.com> wrote:
> Hi all,
>
> we have to figure out a way to work with MINA as it will become soon a TLP.
>
> Currently, ADS 1.0 use MINA 1.0, and it's working great, but we have had
> to wait for a 1.0 version of MINA to be able to release ADS 1.0.
>
> For ADS trunks, wa are facing some problems : as the MINA API has
> changed, ADS is broken in trunks. A decision should be taken regarding
> this kind of problem, because we won't be able to cope with those kind
> of modifications when MINA will be a TLP.
>
> I think that we should depend on a released version of MINA, not on MINA
> trunk, and manage the version through dependencies (thanks to maven,
> this is possible ;)
>
> wdyt ?
>
> Emmanuel
>


-- 
Ersin

Re: MINA Trunks & ADS

Posted by Trustin Lee <tr...@gmail.com>.
On 10/28/06, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Alex Karasulu a écrit :
>
> > Emmanuel Lecharny wrote:
> >
> >> Using externals or using dependencies are two possibilities. My point
> >> was only to prevent project building breakage.
> >>
> >> Btw, I was just wondering if it would not have been better to simply
> >> deprecate the removed class and method of MINA 1.0 instead of
> >> removing them. What is the "politic" regarding such modifications ?
> >
> >
> > Hmmm what specifically were you referring to?  A class was removed in
> > MINA 1.0?
>
> No, a class and some methods were removed in mina trunks.
>
> >
> > Basically up to 1.0 anything goes.  But after 1.0 there should be a
> > deprecation policy in effect.  I don't know how the MINA folks are
> > working that.
>
> ok, I think we agreed on that. Let's ask MINA's guys :)


Even though we reached to 1.0, we are still in course of redesigning API.
Therefore, please stick to 1.0 branch.  It's feature complete and fits
perfectly to LDAP and other related protocols.

Trustin
-- 
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

Re: MINA Trunks & ADS

Posted by Emmanuel Lecharny <el...@gmail.com>.
Alex Karasulu a écrit :

> Emmanuel Lecharny wrote:
>
>> Using externals or using dependencies are two possibilities. My point 
>> was only to prevent project building breakage.
>>
>> Btw, I was just wondering if it would not have been better to simply 
>> deprecate the removed class and method of MINA 1.0 instead of 
>> removing them. What is the "politic" regarding such modifications ?
>
>
> Hmmm what specifically were you referring to?  A class was removed in 
> MINA 1.0?

No, a class and some methods were removed in mina trunks.

>
> Basically up to 1.0 anything goes.  But after 1.0 there should be a 
> deprecation policy in effect.  I don't know how the MINA folks are 
> working that.

ok, I think we agreed on that. Let's ask MINA's guys :)

Emmanuel



Re: MINA Trunks & ADS

Posted by Alex Karasulu <ao...@bellsouth.net>.
Emmanuel Lecharny wrote:
> Using externals or using dependencies are two possibilities. My point 
> was only to prevent project building breakage.
> 
> Btw, I was just wondering if it would not have been better to simply 
> deprecate the removed class and method of MINA 1.0 instead of removing 
> them. What is the "politic" regarding such modifications ?

Hmmm what specifically were you referring to?  A class was removed in 
MINA 1.0?

Basically up to 1.0 anything goes.  But after 1.0 there should be a 
deprecation policy in effect.  I don't know how the MINA folks are 
working that.

Alex

> 
> Emmanuel
> 
> On 10/27/06, *Alex Karasulu* < aok123@bellsouth.net 
> <ma...@bellsouth.net>> wrote:
> 
>     Emmanuel Lecharny wrote:
>      > Hi all,
>      >
>      > we have to figure out a way to work with MINA as it will become
>     soon a TLP.
>      >
>      > Currently, ADS 1.0 use MINA 1.0, and it's working great, but we
>     have had
>      > to wait for a 1.0 version of MINA to be able to release ADS 1.0.
>      >
>      > For ADS trunks, wa are facing some problems : as the MINA API has
>      > changed, ADS is broken in trunks. A decision should be taken
>     regarding
>      > this kind of problem, because we won't be able to cope with those
>     kind
>      > of modifications when MINA will be a TLP.
>      >
>      > I think that we should depend on a released version of MINA, not
>     on MINA
>      > trunk, and manage the version through dependencies (thanks to maven,
>      > this is possible ;)
>      >
>      > wdyt ?
> 
>     Sure when MINA moves we can do this.  However we're also committers on
>     MINA too so it's really semantics here and externals allows us to do
>     many things if used carefully.
> 
>     However experience has shown us that the use of externals can be quite
>     dangerous.  So this is the best route IMO.
> 
>     Alex
> 
> 
> 
> 
> -- 
> Cordialement,
> Emmanuel Lécharny


Re: MINA Trunks & ADS

Posted by Emmanuel Lecharny <el...@gmail.com>.
Using externals or using dependencies are two possibilities. My point was
only to prevent project building breakage.

Btw, I was just wondering if it would not have been better to simply
deprecate the removed class and method of MINA 1.0 instead of removing them.
What is the "politic" regarding such modifications ?

Emmanuel

On 10/27/06, Alex Karasulu <ao...@bellsouth.net> wrote:
>
> Emmanuel Lecharny wrote:
> > Hi all,
> >
> > we have to figure out a way to work with MINA as it will become soon a
> TLP.
> >
> > Currently, ADS 1.0 use MINA 1.0, and it's working great, but we have had
> > to wait for a 1.0 version of MINA to be able to release ADS 1.0.
> >
> > For ADS trunks, wa are facing some problems : as the MINA API has
> > changed, ADS is broken in trunks. A decision should be taken regarding
> > this kind of problem, because we won't be able to cope with those kind
> > of modifications when MINA will be a TLP.
> >
> > I think that we should depend on a released version of MINA, not on MINA
> > trunk, and manage the version through dependencies (thanks to maven,
> > this is possible ;)
> >
> > wdyt ?
>
> Sure when MINA moves we can do this.  However we're also committers on
> MINA too so it's really semantics here and externals allows us to do
> many things if used carefully.
>
> However experience has shown us that the use of externals can be quite
> dangerous.  So this is the best route IMO.
>
> Alex
>



-- 
Cordialement,
Emmanuel Lécharny

Re: MINA Trunks & ADS

Posted by Alex Karasulu <ao...@bellsouth.net>.
Emmanuel Lecharny wrote:
> Hi all,
> 
> we have to figure out a way to work with MINA as it will become soon a TLP.
> 
> Currently, ADS 1.0 use MINA 1.0, and it's working great, but we have had 
> to wait for a 1.0 version of MINA to be able to release ADS 1.0.
> 
> For ADS trunks, wa are facing some problems : as the MINA API has 
> changed, ADS is broken in trunks. A decision should be taken regarding 
> this kind of problem, because we won't be able to cope with those kind 
> of modifications when MINA will be a TLP.
> 
> I think that we should depend on a released version of MINA, not on MINA 
> trunk, and manage the version through dependencies (thanks to maven, 
> this is possible ;)
> 
> wdyt ?

Sure when MINA moves we can do this.  However we're also committers on 
MINA too so it's really semantics here and externals allows us to do 
many things if used carefully.

However experience has shown us that the use of externals can be quite 
dangerous.  So this is the best route IMO.

Alex