[
https://issues.apache.org/jira/browse/OPENJPA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396758#comment-13396758
]
Stevo Slavic commented on OPENJPA-2080:
---------------------------------------
As Romain explained, using old commons-lang 2.x is an issue. I've found this
ticket only after creating OPENJPA-2217, but there I've practically explained
same problem as Romain. Depending on openejb which depends on openjpa brings in
two commons-lang jars, and for what, >90% use is StringUtils. commons-lang 2.x
is compatible with java 1.3. openjpa which by definition requires annotations
and java 5 has fallen under bad influence of commons-lang 2.x by using some of
the java 1.3 compatibility stuff from commons-lang 2.x like
NestableRuntimeException. On the other hand commons-lang3 is targeting java 1.5
making it lighter, typesafe, easier to maintain library, and one wants such
dependencies over legacy ones.
I've attached a patch to OPENJPA-2217 which replaces
commons-lang:commons-lang:2.x with org.apache.commons:commons-lang3:3.1
> Migrate to commons-lang3
> ------------------------
>
> Key: OPENJPA-2080
> URL: https://issues.apache.org/jira/browse/OPENJPA-2080
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Maia Kozheva
> Assignee: Rick Curtis
> Priority: Minor
>
> OpenJPA should migrate from Commons Lang 2.x to 3.x, to eliminate the
> dependency on the old library.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
