[MAGNOLIA-5232] Update version of commons-lang Created: 08/Aug/13  Updated: 12/Aug/15  Resolved: 11/Jun/14

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 5.0.1
Fix Version/s: 5.3

Type: Task Priority: Neutral
Reporter: Daniel Lipp Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-5800 Remove older version of commons-lang Selected
relation
is related to MGNLACTIVATION-87 Update version of commons-lang Closed
is related to MGNLCACHE-62 Update version of commons-lang Closed
is related to MGNLLDAP-84 Update version of commons-lang Closed
is related to MGNLNEWSLETTER-45 Update version of commons-lang Closed
is related to MAGNOLIA-5231 Don't use org.apache.commons.lang.exc... Closed
is related to MAGNOLIA-5972 Update apache commons libraries Closed
is related to MGNLDAM-463 Adapt imports to use new commons-lang... Closed
is related to MGNLWORKFLOW-252 Update to commons-lang 3 Closed
is related to TASKMGMT-12 Remove dependency to commons-lang 2.4 Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Update commons-lang to 3.1

 Description   

We're still using commons-lang 2.4 (released in 2008). We should upgrade to the latest version (3.1 right now).

Caution: new version also got new group- and artifactId:

<dependency>
	<groupId>org.apache.commons</groupId>
	<artifactId>commons-lang3</artifactId>
	<version>3.1</version>
</dependency>

Beware that - for consistency reasons - this should include analyzing all modules (stk, activation, cache, ...) and upgrading them as well...



 Comments   
Comment by Tobias Mattsson [ 04/Dec/13 ]

Here's what the developers say about backwards compatibility:

Lang is now Java 5 based. We've generified the API, moved certain APIs to support varargs and thrown
out any features that are now supported by Java itself. We've removed the deprecated parts of the
API and have also removed some features that were deemed weak or unnecessary. All of this means that
Lang 3.0 is not backwards compatible.

To that end we have changed the package name, allowing Lang 3.0 to sit side-by-side with your
previous version of Lang without any bad side effects. The new package name is the exciting and
original org.apache.commons.lang3. This also forces you to recompile your code, making sure the
compiler can let you know if a backwards incompatibility affects you.
Comment by Milan Divilek [ 11/Jun/14 ]

Reopen:

We found that update of common-langs was done in minor version of ldap module. I will check other modules and in case there was done the same thing I'll revert the change and create new ticket in the proper jira project and with proper version number.

Comment by Milan Divilek [ 11/Jun/14 ]

Reverted from ldap, activation, cache and newsletter as the change there was done in minor version. Created appropriate tickets and linked with this ticket.
I didn't revert the change from imaging and store-client modules as the changes there was done in major version.

Generated at Mon Feb 12 04:03:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.