The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 1 Sep 2003 12:38 AM
Body:
>From what I can tell, the main reason to use XPP3 was the memory leak.
I think there are bigger issues on that front:
- PluginManager caches plugins on a per project basis. In a multiproject build this is
really undesirable.
- The need to evaluate project.xml as an expression, even if it has no variables in it
(MavenUtils). etc
I would like to move this to the 1.1 timeframe
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-627
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-627
Summary: Make Jelly use the xpp3 SAX Driver
Type: Task
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Assignee:
Reporter: Jason van Zyl
Created: Sun, 27 Jul 2003 11:41 PM
Updated: Sun, 27 Jul 2003 11:41 PM
Description:
I couldn't quite get this to work but I know it's possible to make Jelly use the xpp3
SAX driver which would completely eliminate all JAXP dependencies from Maven and we
would strictly be using xpp3. So we could get rid of xerces as a dependency. The xpp3
parser seems to have problems with name spaces but I used a version a couple months of
xpp3 HEAD.
---------------------------------------------------------------------
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]
