The following comment has been added to this issue:
Author: Brett Porter
Created: Wed, 6 Aug 2003 10:12 PM
Body:
what's the justification for not using JAXP?
AFAIK ant also uses JAXP to locate its xerces parser, so as soon as any plugins fire
up it will be sucked down anyway.
If all you want to get rid of is xerces, then that's a different issue - but is that
only because it is heavy, or is it broken? If its a haviness issue, I don't see why
this needs to be fixed before 1.1. Potentially a lot of things will need to be tested
if maven only provides xpp3 I imagine.
---------------------------------------------------------------------
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.0-rc1
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]
