Jasha, I find this issue weird.
I just checked with mvn dependency:tree and (without your patch) see
commons-lang-2.6 being included, as I would expect. We have commons-lang
explicitly specified, as well as its version (2.6) configured in the
dependency-management (rave-project). That should always ensure version 2.6 is
selected as its a direct/explicit dependency, no matter what transitively
derived version would be needed for openjpa (or any other).
Can you please check (without your patch) what outcome you have with mvn
dependency:tree?
If in your case maven hides the 2.6 version it should say so. Please send you
output then to the list (or on the issue) because then something else must be wrong.
At any rate, depending on "order of definition" within a pom isn't a reliable
and good enough solution IMO.
Regards,
Ate
On 06/21/2011 02:35 PM, Jasha Joachimsthal (JIRA) wrote:
[
https://issues.apache.org/jira/browse/RAVE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jasha Joachimsthal updated RAVE-81:
-----------------------------------
Attachment: RAVE-81_fix_order_in_which_commons-lang_is_loaded.patch
The order in which the artifacts are defined in the pom influences the version
during compile time. Moving commons-lang above openjpa-all does the trick.
Fix classloading issue for StringUtils in ModelUtilsTest
--------------------------------------------------------
Key: RAVE-81
URL: https://issues.apache.org/jira/browse/RAVE-81
Project: Rave
Issue Type: Sub-task
Affects Versions: 0.1-INCUBATING
Reporter: Jasha Joachimsthal
Assignee: Jasha Joachimsthal
Priority: Minor
Fix For: 0.2-INCUBATING
Attachments: RAVE-81_fix_order_in_which_commons-lang_is_loaded.patch
ModelUtilsTest contains a isAllLowercase which was introduced in commons-lang
2.5
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
