[WARNING]   While downloading xml-apis:xml-apis:2.0.2    This artifact has been 
relocated to xml-apis:xml-apis:1.0.b2
---------------------------------------------------------------------------------------------------------------------

         Key: MEV-222
         URL: http://jira.codehaus.org/browse/MEV-222
     Project: Maven Evangelism
        Type: Bug
    Reporter: Brian Bonner


Last Friday I started getting the problem related to:  MEV-217  now, I'm 
getting this error  (also apparently due to relocations).

It appears that 2 things happen.  This problem manifested itself in two ways:

The first symptom was that all of the XFire test cases related to xerces were 
failing (thanks, Dan)

javax.xml.parsers.FactoryConfigurationError: Provider for 
javax.xml.parsers.DocumentBuilderFactory cannot be found
        at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)


The second symptom was the warning I received in my log:

[DEBUG]   wsdl4j:wsdl4j:jar:1.4 (selected for compile)
[DEBUG]   xalan:xalan:jar:2.7.0 (selected for test)
[WARNING] While downloading xml-apis:xml-apis:2.0.2
  This artifact has been relocated to xml-apis:xml-apis:1.0.b2.


[DEBUG]     xml-apis:xml-apis:jar:1.0.b2 (selected for test)
[DEBUG]   httpunit:httpunit:jar:1.5.1 (selected for compile)


If you visit:  xalan's pom at:  
http://public.planetmirror.com/pub/maven2/xalan/xalan/2.7.0/xalan-2.7.0.pom

You'll see that it has two dependencies:  xml-apis:xml-apis:jar:2.0.2  and 
xerces:xercesImpl:2.6.0


First, I'm not sure if the relocation is correct.  It seems wierd.  Also,  the 
pom for:  
http://public.planetmirror.com/pub/maven2/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.pom
  has:

<downloadUrl>http://www.apache.org/dist/xml/commons/binaries/xml-commons-1.0.b2.tar.gz</downloadUrl>

When you visit this URL, I'm not sure these are the xml-apis at all.  These 
look like they are all for the catalog resolver (namespace resolution).

Second, I'm not sure the xerces dependency should be failing after the 
relocation.  That's what I was seeing with the spring problem.  When maven2 
encountered a relocation, it wouldn't pickup the dependency at all.


-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to