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* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> 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
