[VOTE] Release Wagon version 1.0-beta-7
Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=15972 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10335&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-005/ Staging site: http://maven.apache.org/wagon-1.0-beta-7/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven Linkcheck Plugin 1.1 Released
The Maven team is pleased to announce the release of the Maven Linkcheck Plugin, version 1.1 This plug-in allows you to generate a Linkcheck report of your project's documentation using the Doxia Linkcheck Tool. http://maven.apache.org/plugins/maven-linkcheck-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-linkcheck-plugin 1.1 Release Notes - Maven 2.x Linkcheck Plugin - Version 1.1 ** Bug * [MLINKCHECK-2] - links to reports give false positives if run from a profile * [MLINKCHECK-3] - Cannot add excludedHttpStatusErrors configuration * [MLINKCHECK-6] - IllegalArgumentException for some URIs * [MLINKCHECK-8] - Adding configuration for excludeLinks suppresses warnings * [MLINKCHECK-9] - The necessary images are not included in the generated site, if you use a custom skin ** Improvement * [MLINKCHECK-4] - Add support for wildcards in excludedPages Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Doxia 1.1.4 and Maven Doxia Sitetools 1.1.4
Hi, We solved 4+2 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780&styleName=Html&version=16702 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624&styleName=Html&version=16694 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10780&status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11624&status=1 Staging repo: https://repository.apache.org/content/repositories/maven-058/ Staging sites: http://maven.apache.org/doxia/doxia-1.1.4/ http://maven.apache.org/doxia/doxia-sitetools-1.1.4/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need help with test failure in doxia-sitetools, which is blocking the release
On 2010-11-13 18:21, Lukas Theussl wrote: > > > Dennis Lundberg wrote: >> On 2010-11-13 17:47, Dennis Lundberg wrote: >>> On 2010-11-13 17:24, Lukas Theussl wrote: I can confirm this but I have no idea right now (what does "Server Error" mean?). >>> >>> Right, not the most useful error message... >> >> After enhancing the error message I get this when running the failing >> test: >> >> >> Caused by: java.io.IOException: Method failed: 'Server Error' when >> accessing the URL 'http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent'. >> Status code=500 >> >> The parser requires a status code of 200. >> >> I had problems trying to fetch that URL from IDEA as well. >> >> The question is how to deal with it. Do we download that resource and >> put it locally among the other test resources, and reference it as such >> in the test case? It would feel just wrong to change the parser to allow >> status 500. > > Yes, the tests should not depend on whether a resource is available > online or not. I would also prefer you adapt your commit r1033377 [1] so > as to not require a network connection for the tests. Done. Some googling found the answer to why the problems occured: http://www.vineetmanohar.com/2010/11/w3-org-dtds-blocked-from-java-http-500/ I have a patch locally that changes the user-agent header to get around this, if we should need it later on. I'm not including it in this release though. > In general, validation and entity resolution should use local resources > whenever possible, see DOXIA-388, MSITE-440. > > Cheers, > -Lukas > > > [1] http://svn.apache.org/viewvc?view=revision&revision=1033377 > >> >>> I have checked out the 1.1.3 tag and it builds fine, so it must be some recent change, maybe the httpclient upgrade? >>> >>> Yes, that could be it. Thanks! >>> -Lukas Dennis Lundberg wrote: > Hi > > After fixing a test failure (at least I thought so) in r10033377 > [1] for > doxia-sitetools, I went ahead to release doxia and doxia-sitetools > 1.1.4. This fails during doxia-sitetools because of a test failure on > both Windows And Ubuntu. It has to with validating an xdoc document > that > specifies entities. This test was added in version 1.1.3 as > DOXIASITETOOLS-37 [2], so it has passed a release before. > > > Here's my Surefire Report: > > --- > > > Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest > --- > > > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 > sec<<< FAILURE! > testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) > >Time elapsed: 36.094 sec<<< ERROR! > org.apache.maven.doxia.siterenderer.RendererException: Error parsing > 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': > > > line [-1] Error validating the model: Method failed: Server Error > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) > > > at > org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) > > > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) > > > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > > > at > org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) > > > Caused by: org.apache.maven.doxia.parser.ParseException: Error > validating the model: Method failed: Server Error > at > org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) > > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) > > > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) > > > ... 30 more > Caused by: java.io.IOException: Method failed: Server Error > at > org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) > > > at > org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) > > > at > org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown > Source) > at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown > Source) > at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown > Source) > at org.
Re: Need help with test failure in doxia-sitetools, which is blocking the release
Dennis Lundberg wrote: On 2010-11-13 17:47, Dennis Lundberg wrote: On 2010-11-13 17:24, Lukas Theussl wrote: I can confirm this but I have no idea right now (what does "Server Error" mean?). Right, not the most useful error message... After enhancing the error message I get this when running the failing test: Caused by: java.io.IOException: Method failed: 'Server Error' when accessing the URL 'http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent'. Status code=500 The parser requires a status code of 200. I had problems trying to fetch that URL from IDEA as well. The question is how to deal with it. Do we download that resource and put it locally among the other test resources, and reference it as such in the test case? It would feel just wrong to change the parser to allow status 500. Yes, the tests should not depend on whether a resource is available online or not. I would also prefer you adapt your commit r1033377 [1] so as to not require a network connection for the tests. In general, validation and entity resolution should use local resources whenever possible, see DOXIA-388, MSITE-440. Cheers, -Lukas [1] http://svn.apache.org/viewvc?view=revision&revision=1033377 I have checked out the 1.1.3 tag and it builds fine, so it must be some recent change, maybe the httpclient upgrade? Yes, that could be it. Thanks! -Lukas Dennis Lundberg wrote: Hi After fixing a test failure (at least I thought so) in r10033377 [1] for doxia-sitetools, I went ahead to release doxia and doxia-sitetools 1.1.4. This fails during doxia-sitetools because of a test failure on both Windows And Ubuntu. It has to with validating an xdoc document that specifies entities. This test was added in version 1.1.3 as DOXIASITETOOLS-37 [2], so it has passed a release before. Here's my Surefire Report: --- Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 sec<<< FAILURE! testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) Time elapsed: 36.094 sec<<< ERROR! org.apache.maven.doxia.siterenderer.RendererException: Error parsing 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': line [-1] Error validating the model: Method failed: Server Error at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) Caused by: org.apache.maven.doxia.parser.ParseException: Error validating the model: Method failed: Server Error at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) ... 30 more Caused by: java.io.IOException: Method failed: Server Error at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) ... 32 more To be able to recreate this you need to downgrade the property in t
Re: Need help with test failure in doxia-sitetools, which is blocking the release
On 2010-11-13 17:47, Dennis Lundberg wrote: > On 2010-11-13 17:24, Lukas Theussl wrote: >> >> I can confirm this but I have no idea right now (what does "Server >> Error" mean?). > > Right, not the most useful error message... After enhancing the error message I get this when running the failing test: Caused by: java.io.IOException: Method failed: 'Server Error' when accessing the URL 'http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent'. Status code=500 The parser requires a status code of 200. I had problems trying to fetch that URL from IDEA as well. The question is how to deal with it. Do we download that resource and put it locally among the other test resources, and reference it as such in the test case? It would feel just wrong to change the parser to allow status 500. > >> I have checked out the 1.1.3 tag and it builds fine, so >> it must be some recent change, maybe the httpclient upgrade? > > Yes, that could be it. Thanks! > >> -Lukas >> >> >> Dennis Lundberg wrote: >>> Hi >>> >>> After fixing a test failure (at least I thought so) in r10033377 [1] for >>> doxia-sitetools, I went ahead to release doxia and doxia-sitetools >>> 1.1.4. This fails during doxia-sitetools because of a test failure on >>> both Windows And Ubuntu. It has to with validating an xdoc document that >>> specifies entities. This test was added in version 1.1.3 as >>> DOXIASITETOOLS-37 [2], so it has passed a release before. >>> >>> >>> Here's my Surefire Report: >>> >>> --- >>> >>> Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest >>> --- >>> >>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 >>> sec<<< FAILURE! >>> testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) >>> Time elapsed: 36.094 sec<<< ERROR! >>> org.apache.maven.doxia.siterenderer.RendererException: Error parsing >>> 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': >>> >>> line [-1] Error validating the model: Method failed: Server Error >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) >>> >>> at >>> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) >>> >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) >>> >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) >>> >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) >>> >>> Caused by: org.apache.maven.doxia.parser.ParseException: Error >>> validating the model: Method failed: Server Error >>> at >>> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) >>> >>> at >>> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) >>> >>> ... 30 more >>> Caused by: java.io.IOException: Method failed: Server Error >>> at >>> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) >>> >>> at >>> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) >>> >>> at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown >>> Source) >>> at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown >>> Source) >>> at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown >>> Source) >>> at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) >>> at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown >>> Source) >>> at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) >>> at >>> org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown >>> Source) >>> at >>> org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown >>> >>> Source) >>> at >>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown >>> >>> Source) >>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) >>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) >>> at >>> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) >>> ... 32 more >>> >>> >>> To be able to recreate this you need to downgrade the property >>> in the main POM of doxia-sitetools from 1.1.4 to >>> 1.1.4-SNAPSHOT. Doxia 1.1.4 is currently on
RE: Need help with test failure in doxia-sitetools, which is blocking the release
I've reproduced the failing test too. Let me see if I can find some time to have a look at it too. - Robert > Date: Sat, 13 Nov 2010 17:47:16 +0100 > From: denn...@apache.org > To: dev@maven.apache.org > Subject: Re: Need help with test failure in doxia-sitetools, which is > blocking the release > > On 2010-11-13 17:24, Lukas Theussl wrote: > > > > I can confirm this but I have no idea right now (what does "Server > > Error" mean?). > > Right, not the most useful error message... > > > I have checked out the 1.1.3 tag and it builds fine, so > > it must be some recent change, maybe the httpclient upgrade? > > Yes, that could be it. Thanks! > > > -Lukas > > > > > > Dennis Lundberg wrote: > >> Hi > >> > >> After fixing a test failure (at least I thought so) in r10033377 [1] for > >> doxia-sitetools, I went ahead to release doxia and doxia-sitetools > >> 1.1.4. This fails during doxia-sitetools because of a test failure on > >> both Windows And Ubuntu. It has to with validating an xdoc document that > >> specifies entities. This test was added in version 1.1.3 as > >> DOXIASITETOOLS-37 [2], so it has passed a release before. > >> > >> > >> Here's my Surefire Report: > >> > >> --- > >> > >> Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest > >> --- > >> > >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 > >> sec<<< FAILURE! > >> testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) > >> Time elapsed: 36.094 sec<<< ERROR! > >> org.apache.maven.doxia.siterenderer.RendererException: Error parsing > >> 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': > >> > >> line [-1] Error validating the model: Method failed: Server Error > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) > >> > >> at > >> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) > >> > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) > >> > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) > >> > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) > >> > >> Caused by: org.apache.maven.doxia.parser.ParseException: Error > >> validating the model: Method failed: Server Error > >> at > >> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) > >> > >> at > >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) > >> > >> ... 30 more > >> Caused by: java.io.IOException: Method failed: Server Error > >> at > >> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) > >> > >> at > >> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) > >> > >> at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown > >> Source) > >> at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown > >> Source) > >> at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown > >> Source) > >> at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) > >> at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown > >> Source) > >> at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) > >> at > >> org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown > >> Source) > >> at > >> org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown > >> > >> Source) > >> at > >> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > >> > >> Source) > >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > >> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > >> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > >> at > >> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) > >> ... 32 more > >> > >> > >> To be able to recreate this you need to downgrade the property > >> in the main POM of doxia-sitetools from 1.1.4 to > >> 1.1.4-SNAPSHOT. Doxia 1.1.4 is currently on my local machine and in an > >> unclosed staging repo. I was planning to put doxia and doxia-sitetools > >> in the same staging repo. > >> > >> Any hints? > >> > >> > >> [1] http://svn.apache.org/viewvc?rev=1033377&view=rev > >> [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-37 > >> > > > > ---
Re: Need help with test failure in doxia-sitetools, which is blocking the release
On 2010-11-13 17:24, Lukas Theussl wrote: > > I can confirm this but I have no idea right now (what does "Server > Error" mean?). Right, not the most useful error message... > I have checked out the 1.1.3 tag and it builds fine, so > it must be some recent change, maybe the httpclient upgrade? Yes, that could be it. Thanks! > -Lukas > > > Dennis Lundberg wrote: >> Hi >> >> After fixing a test failure (at least I thought so) in r10033377 [1] for >> doxia-sitetools, I went ahead to release doxia and doxia-sitetools >> 1.1.4. This fails during doxia-sitetools because of a test failure on >> both Windows And Ubuntu. It has to with validating an xdoc document that >> specifies entities. This test was added in version 1.1.3 as >> DOXIASITETOOLS-37 [2], so it has passed a release before. >> >> >> Here's my Surefire Report: >> >> --- >> >> Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest >> --- >> >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 >> sec<<< FAILURE! >> testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) >> Time elapsed: 36.094 sec<<< ERROR! >> org.apache.maven.doxia.siterenderer.RendererException: Error parsing >> 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': >> >> line [-1] Error validating the model: Method failed: Server Error >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) >> >> at >> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) >> >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) >> >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) >> >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) >> >> Caused by: org.apache.maven.doxia.parser.ParseException: Error >> validating the model: Method failed: Server Error >> at >> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) >> >> at >> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) >> >> ... 30 more >> Caused by: java.io.IOException: Method failed: Server Error >> at >> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) >> >> at >> org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) >> >> at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown >> Source) >> at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown >> Source) >> at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown >> Source) >> at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) >> at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown >> Source) >> at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) >> at >> org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown >> Source) >> at >> org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown >> >> Source) >> at >> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown >> >> Source) >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) >> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) >> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) >> at >> org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) >> ... 32 more >> >> >> To be able to recreate this you need to downgrade the property >> in the main POM of doxia-sitetools from 1.1.4 to >> 1.1.4-SNAPSHOT. Doxia 1.1.4 is currently on my local machine and in an >> unclosed staging repo. I was planning to put doxia and doxia-sitetools >> in the same staging repo. >> >> Any hints? >> >> >> [1] http://svn.apache.org/viewvc?rev=1033377&view=rev >> [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-37 >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Need help with test failure in doxia-sitetools, which is blocking the release
I can confirm this but I have no idea right now (what does "Server Error" mean?). I have checked out the 1.1.3 tag and it builds fine, so it must be some recent change, maybe the httpclient upgrade? -Lukas Dennis Lundberg wrote: Hi After fixing a test failure (at least I thought so) in r10033377 [1] for doxia-sitetools, I went ahead to release doxia and doxia-sitetools 1.1.4. This fails during doxia-sitetools because of a test failure on both Windows And Ubuntu. It has to with validating an xdoc document that specifies entities. This test was added in version 1.1.3 as DOXIASITETOOLS-37 [2], so it has passed a release before. Here's my Surefire Report: --- Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 sec<<< FAILURE! testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) Time elapsed: 36.094 sec<<< ERROR! org.apache.maven.doxia.siterenderer.RendererException: Error parsing 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': line [-1] Error validating the model: Method failed: Server Error at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) Caused by: org.apache.maven.doxia.parser.ParseException: Error validating the model: Method failed: Server Error at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) ... 30 more Caused by: java.io.IOException: Method failed: Server Error at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) ... 32 more To be able to recreate this you need to downgrade the property in the main POM of doxia-sitetools from 1.1.4 to 1.1.4-SNAPSHOT. Doxia 1.1.4 is currently on my local machine and in an unclosed staging repo. I was planning to put doxia and doxia-sitetools in the same staging repo. Any hints? [1] http://svn.apache.org/viewvc?rev=1033377&view=rev [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-37 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Need help with test failure in doxia-sitetools, which is blocking the release
Hi After fixing a test failure (at least I thought so) in r10033377 [1] for doxia-sitetools, I went ahead to release doxia and doxia-sitetools 1.1.4. This fails during doxia-sitetools because of a test failure on both Windows And Ubuntu. It has to with validating an xdoc document that specifies entities. This test was added in version 1.1.3 as DOXIASITETOOLS-37 [2], so it has passed a release before. Here's my Surefire Report: --- Test set: org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.125 sec <<< FAILURE! testRender(org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest) Time elapsed: 36.094 sec <<< ERROR! org.apache.maven.doxia.siterenderer.RendererException: Error parsing 'G:\apache\maven\trunks\doxia\doxia-sitetools\doxia-site-renderer\src\test\resources\site-validate\xdoc\entityTest.xml': line [-1] Error validating the model: Method failed: Server Error at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:418) at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:330) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.doxia.siterenderer.DefaultSiteRendererTest.testRender(DefaultSiteRendererTest.java:132) Caused by: org.apache.maven.doxia.parser.ParseException: Error validating the model: Method failed: Server Error at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:112) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.validate(DefaultSiteRenderer.java:879) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:399) ... 30 more Caused by: java.io.IOException: Method failed: Server Error at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.toByteArray(AbstractXmlParser.java:810) at org.apache.maven.doxia.parser.AbstractXmlParser$CachedFileEntityResolver.resolveEntity(AbstractXmlParser.java:739) at org.apache.xerces.util.EntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.startPE(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.skipSeparator(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDecls(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.scanDTDInternalSubset(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.maven.doxia.util.XmlValidator.validate(XmlValidator.java:108) ... 32 more To be able to recreate this you need to downgrade the property in the main POM of doxia-sitetools from 1.1.4 to 1.1.4-SNAPSHOT. Doxia 1.1.4 is currently on my local machine and in an unclosed staging repo. I was planning to put doxia and doxia-sitetools in the same staging repo. Any hints? [1] http://svn.apache.org/viewvc?rev=1033377&view=rev [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-37 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Release Maven Linkcheck Plugin version 1.1 and Doxia Tools 1.2
Hi, The vote has passed with the following result : +1 (binding): Lukas Theussl, Olivier Lamy, Vincent Siveton, Dennis Lundberg +1 (non binding): Tony Chemit I will promote the artifacts to the central repo. Thanks to everyone who took the time to review this release! On 2010-11-09 21:32, Dennis Lundberg wrote: > Hi, > > We solved 6 + 3 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16748 > http://jira.codehaus.org/browse/DOXIA-410 > http://jira.codehaus.org/browse/DOXIA-412 > http://jira.codehaus.org/browse/DOXIA-414 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12100&status=1 > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DOXIA+AND+resolution+%3D+Unresolved+AND+component+%3D+%22Doxia+Tools%22+ORDER+BY+priority+DESC&mode=hide > > Staging repo: > https://repository.apache.org/content/repositories/maven-051/ > > Staging sites: > http://maven.apache.org/plugins/maven-linkcheck-plugin-1.1/ > http://maven.apache.org/doxia/doxia-tools-1.2/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.1 and Doxia Tools 1.2
+1 from me On 2010-11-09 21:32, Dennis Lundberg wrote: > Hi, > > We solved 6 + 3 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12100&styleName=Html&version=16748 > http://jira.codehaus.org/browse/DOXIA-410 > http://jira.codehaus.org/browse/DOXIA-412 > http://jira.codehaus.org/browse/DOXIA-414 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12100&status=1 > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DOXIA+AND+resolution+%3D+Unresolved+AND+component+%3D+%22Doxia+Tools%22+ORDER+BY+priority+DESC&mode=hide > > Staging repo: > https://repository.apache.org/content/repositories/maven-051/ > > Staging sites: > http://maven.apache.org/plugins/maven-linkcheck-plugin-1.1/ > http://maven.apache.org/doxia/doxia-tools-1.2/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
