But the new svn trunk don't have the lang package, just the lang3.
So the code that depends on the old stuff don't work.

-- Wellington B. de Carvalho


On Thu, Apr 15, 2010 at 12:27 PM, James Carman
<ja...@carmanconsulting.com>wrote:

> The Commons Lang library isn't intended to be "mixed and matched"
> between releases like that.  The package is released as a whole.  You
> can't expect to pick stuff out of different releases and then just
> combine them and somehow expect them to work.
>
> The reason the package name is changing is so that the next-generation
> work on Commons Lang can move forward.  This way, even if you still
> have an old version of Commons Lang in your classpath (because of a
> third-party dependency) and you want to use Lang3, you can still do
> it.  The code that depends on the old stuff will work just fine and
> the code that depends on the new stuff will work just fine.
>
> On Thu, Apr 15, 2010 at 11:04 AM, Tom Brito <brito....@gmail.com> wrote:
> > Hi all!
> >
> > I would like to know why this incompatibility between the jar file and
> the
> > svn repository:
> > In the jar file there is the package org.apache.commons.lang;
> > This same package in svn is called org.apache.commons.lang3
> >
> > As consequence, I can't use code directly from svn, becouse it will not
> run
> > with the jar.
> > Anyone know why this incompatibility?
> >
> > Thanks!
> >
> >
> > -- Wellington B. de Carvalho
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
>
>

Reply via email to