Hi, The problem here is that the actual fetching is done inside XmlUnit, which is only a tool we use to assert that the generated deployment descriptor is equal to the expected one.
Do you know if it's possible to tell XmlUnit to *not* fetch the DTDs? I haven't used XmlUnit myself, I'm only trying to make sure there are no clouds in Jenkins. Benson Margulies skrev 2011-04-26 21:17: > Then use a resolver to do the check instead of actually fetching? > > On Tue, Apr 26, 2011 at 1:30 PM, Dennis Lundberg <[email protected]> wrote: >> Benson Margulies skrev 2011-04-25 22:48: >>> fix the tests to have a catalog to point to local copies >> >> Yes, it is always best to use local copies of DTDs and XSDs for tests, >> but in this case that would be difficult to do. We are testing to see >> that the generated deployment descriptor matches the expected one, and >> we expect it to declare the DTD pointing to its canonical location, >> which is the Sun website. >> >>> >>> On Apr 25, 2011, at 4:28 PM, Dennis Lundberg <[email protected]> wrote: >>> >>>> Hi >>>> >>>> The job maven-plugins-ITs-2.x [3] is also failing. It is the ITs for >>>> Maven EAR Plugin that fails. I did some digging around and have found >>>> out the cause. >>>> >>>> The ITs use XmlUnit to check that the deployment descriptors are >>>> correct. When XmlUnit loads the deployment descriptor it reads its DTD >>>> from http://java.sun.com/dtd/application_1_3.dtd. However the >>>> java.sun.com site seems very unresponsive and frequently times out, >>>> generating exceptions like the one below. >>>> >>>> I don't know how to best solve this. Any advise would be appreciated. >>>> >>>> >>>> >>>> java.net.ConnectException: Connection timed out: connect >>>> at java.net.PlainSocketImpl.socketConnect(Native Method) >>>> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) >>>> at >>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) >>>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) >>>> at java.net.Socket.connect(Socket.java:524) >>>> at java.net.Socket.connect(Socket.java:474) >>>> at sun.net.NetworkClient.doConnect(NetworkClient.java:157) >>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) >>>> at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) >>>> at sun.net.www.http.HttpClient.<init>(HttpClient.java:231) >>>> at sun.net.www.http.HttpClient.New(HttpClient.java:304) >>>> at sun.net.www.http.HttpClient.New(HttpClient.java:321) >>>> at >>>> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:839) >>>> at >>>> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:791) >>>> at >>>> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:716) >>>> at >>>> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:960) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:973) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:905) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:872) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:282) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1021) >>>> at >>>> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) >>>> at >>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) >>>> at >>>> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) >>>> at >>>> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) >>>> at >>>> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) >>>> at >>>> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) >>>> at org.custommonkey.xmlunit.XMLUnit.buildDocument(XMLUnit.java:382) >>>> at org.custommonkey.xmlunit.XMLUnit.buildDocument(XMLUnit.java:369) >>>> at org.custommonkey.xmlunit.Diff.<init>(Diff.java:101) >>>> at >>>> org.apache.maven.plugin.ear.it.AbstractEarPluginIT.assertDeploymentDescriptors(AbstractEarPluginIT.java:397) >>>> >>>> ... >>>> >>>> >>>> >>>> [3] >>>> https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-plugins-ITs-2.x/ >>>> >>>> Dennis Lundberg skrev 2011-04-22 11:51: >>>>> Hi >>>>> >>>>> There are a numbers of problems that prevents our plugins from building >>>>> successfully in the ASF Jenkins instance. I've fixed what I can, but >>>>> there are some outstanding issues that I need help fixing. >>>>> >>>>> >>>>> Maven GPG Plugin >>>>> >>>>> When building plugins with ITs [1] the build fails in Jenkins because >>>>> there is no gpg available on the path on the build machine. I guess we >>>>> need to contact Infra to request that gpg is installed. >>>>> >>>>> >>>>> Maven Patch Plugin >>>>> >>>>> When building plugins with ITs [1] the build fails in Jenkins because of >>>>> an invalid option "-E" to the patch program on the build machine. >>>>> >>>>> >>>>> Maven Dependency Plugin >>>>> >>>>> When building plugins without ITs [2] the build fails in Jenkins because >>>>> of unit test failures. I can not replicate these failures on my local >>>>> Windows 7 machine. >>>>> >>>>> Failed tests: >>>>> testOverWriteRelease(org.apache.maven.plugin.dependency.TestCopyDependenciesMojo) >>>>> testOverWriteSnap(org.apache.maven.plugin.dependency.TestCopyDependenciesMojo) >>>>> testCopyOverWriteReleases(org.apache.maven.plugin.dependency.fromConfiguration.TestCopyMojo) >>>>> testCopyOverWriteSnapshot(org.apache.maven.plugin.dependency.fromConfiguration.TestCopyMojo) >>>>> testCopyOverWriteIfNewer(org.apache.maven.plugin.dependency.fromConfiguration.TestCopyMojo) >>>>> >>>>> >>>>> Maven Javadoc Plugin >>>>> >>>>> When building plugins without ITs [2] the build failed yesterday in >>>>> Jenkins because of unit test failures, but succeeded today even though >>>>> no changes were made to the code. I can replicate this failure on my >>>>> local Windows 7 machine. >>>>> >>>>> Failed tests: >>>>> testProxy(org.apache.maven.plugin.javadoc.JavadocReportTest) >>>>> >>>>> >>>>> [1] >>>>> https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-plugins-ITs-2.x/ >>>>> >>>>> [2] >>>>> https://builds.apache.org/hudson/view/M-R/view/Maven/job/maven-plugins/ >>>>> >>>> >>>> >>>> -- >>>> Dennis Lundberg >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> -- >> Dennis Lundberg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
