The following comment has been added to this issue:
Author: Joakim Erdfelt
Created: Wed, 25 Feb 2004 8:28 AM
Body:
I have found a trick that allows us 1.0-RC1 users to get around the issues with
regards to the commons-lang dependency in the maven core and/or other plugins.
I use the following inside of my plugins and/or projects to get the benefits of
commons-lang-2.0.jar in my builds, plugin.jelly, and maven.xml.
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.0</version>
<properties>
<war.bundle>true</war.bundle>
<webveer.lib>true</webveer.lib>
<!-- this is done to avoid a conflict with
commons-lang-1.0.1.jar from the higher
level plugins. -->
<classloader>root.maven</classloader>
</properties>
</dependency>
NOTE: If the switch is made to commons-lang-2.0 then you get the benefit of other
objects such as StringEscapeUtils.
http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/StringEscapeUtils.html
This unified xml/html/java/javascript escaping object would make resolving of some
xdoc bugs ( MPXDOC-82 / MPXDOC-66 / MPXDOC-82 / MPXDOC-27 / MPXDOC-11 / MPXDOC-17 )
easier.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1153&page=comments#action_17118
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1153
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1153
Summary: update commons-lang dependency
Type: Improvement
Status: Open
Priority: Trivial
Original Estimate: 5 minutes
Time Spent: Unknown
Remaining: 5 minutes
Project: maven
Fix Fors:
1.0-rc2
Versions:
1.0-rc2
Assignee: Brett Porter
Reporter: fabrizio giustina
Created: Sat, 7 Feb 2004 10:54 AM
Updated: Wed, 25 Feb 2004 8:28 AM
Description:
actually maven dependencies include commons-lang 1.0-b1.1.
It would be better to update it to commons-lang 2.0: the new release is totally
compatible with the old (no methods have been removed) and this will allows to use new
useful string utils method in plugin (replace, trim, ...).
Actually also if you include a commons-lang 2.0 dependency in a plugin it seems you
are not able to call commons-lang 2.0 methods from jelly, since it always find the old
commons-lang 1.0 classes in maven classloader first (unless specifing a root
classloader in dependency).
Change: modify in project.xml
<dependency>
<id>commons-lang</id>
<version>1.0-b1.1</version>
<url>http://jakarta.apache.org/commons/</url>
</dependency>
with:
<dependency>
<artifactId>commons-lang</artifactId>
<groupId>commons-lang</groupId>
<version>2.0</version>
<url>http://jakarta.apache.org/commons/</url>
</dependency>
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
