commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <pbened...@apache.org>
Subject Re: [LANG] incompatibility of jar with svn
Date Thu, 15 Apr 2010 16:37:23 GMT
Great,

Thanks James and sebb. Then all a user needs to do is declare both
jars in a POM and things should be fine.

Paul

On Thu, Apr 15, 2010 at 11:29 AM, James Carman
<james@carmanconsulting.com> wrote:
> Yes, you can have code that uses both versions in your code.  What I
> meant was that we support the codebase as a whole, publishable unit.
> We don't expect folks to pick pieces out of different releases and try
> to combine them.
>
> The group id has been renamed to org.apache.commons already
> (http://svn.apache.org/repos/asf/commons/proper/lang/trunk/pom.xml),
> so you really can have two different versions in your maven project.
> One might argue that the artifactId should be commons-lang3 for
> consistency with later releases, but since we don't have any lang
> releases in the org.apache.commons group yet, it's not that big of a
> deal I guess (I'd prefer lang3 in the artifactId too).
>
> On Thu, Apr 15, 2010 at 12:20 PM, Paul Benedict <pbenedict@apache.org> wrote:
>> James,
>>
>> Actually, I believe Lang 3 is supposed to be mixed and matched. That
>> is why the package was renamed. What I think we have here are symptoms
>> of an incomplete transition. If we really want mixing/matching, the
>> groupId should be renamed too; otherwise, we should revert the package
>> name.
>>
>> Paul
>>
>> On Thu, Apr 15, 2010 at 11:16 AM, Tom Brito <brito.pro@gmail.com> wrote:
>>> 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
>>> <james@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.pro@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-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: user-help@commons.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>> For additional commands, e-mail: user-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org


Mime
View raw message