You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2013/11/13 17:33:24 UTC
Can somebody (Hervé?) stage the Doxia 1.5 site
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[INFO] Downloading from JIRA at:
http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&statusIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=1000&reset=true&decorator=none
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:753)
at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.xml.sax.SAXParseException; lineNumber: 117; columnNumber: 3;
The element type "meta" must be terminated by the matching end-tag
"</meta>".
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
... 30 more
[INFO]
[INFO] --- maven-site-plugin:3.2:deploy (default-deploy) @ doxia ---
[INFO] Parent project loaded from repository:
org.apache.maven:maven-parent:pom:23
[INFO] Parent project loaded from repository: org.apache:apache:pom:13
[ERROR]
Unsupported protocol: 'scm' for site deployment to
distributionManagement.site.url=scm:svn:
https://svn.apache.org/repos/infra/websites/production/maven/content/.
Currently supported protocols are: http, file, https.
Protocols may be added through wagon providers.
For more information, see
http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Hervé BOUTEMY <he...@free.fr>.
yeah, the svn commit is quite long
did you realize there are 3800 files, for 72MB?
this quite long svn commit is the price to pay for a not so long push to
effective site, since the site is a sum of a lot of such large components
documentations, so rsync required mutliple hours of sync before svnpubsub
notice that this is the reason why I promote publishing to <artifactId>-LATEST
then svn cp+rm operations, instead of using profiles to publish multiple times
to different locations
I once hoped that we could publish only one complete zip archive of component
documentation site then let the site serve archive content as if it was
unarchived: this would count only for 1 not-so-large (due to compression) file
But I never found a way to implement such a thing. And never found anybody
understanding me and able to find an implementation...
Regards,
Hervé
Le jeudi 14 novembre 2013 23:44:41 Stephen Connolly a écrit :
> On 14 November 2013 23:33, Hervé BOUTEMY <he...@free.fr> wrote:
> > Le jeudi 14 novembre 2013 20:35:18 Stephen Connolly a écrit :
> > > Cool. I'll give it a shot after getting some people to bed... Are the
> > > instructions on
> > > http://maven.apache.org/developers/release/maven-shared-release.htmlcorr
> > > ect
> > > w.r.t. Staging the doxia site, or is there some crazy-ass pub-sub
> > > incantation I must invoke to stage the site?
> >
> > no, these instructions are not ok, mainly because Doxia is a multi-module
> > project
> > So you really have to follow [1]
> > ie:
> > 1. generate site
> > 2. stage
> > 3. invoke scm-publish explicitely (and not hidden in site-deploy phase)
>
> scm-publish is dog slow... still transmitting the commit... after 45 minutes
> > Regards,
> >
> > Hervé
> >
> >
> > [1]
> > http://maven.apache.org/developers/website/deploy-component-reference-docu
> > mentation.html>
> > > On Thursday, 14 November 2013, Hervé BOUTEMY wrote:
> > > > m-site-p configuration fixed
> > > >
> > > > and compatibility tested in dist-tool-plugin: see
> > > > http://svn.apache.org/r1541998[1]
> > > >
> > > > we only need Markdown module, the incompatibility is in doxia-core
> >
> > only,
> >
> > > > but it's
> > > > not a problem
> > > >
> > > > so ready for the new release :)
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le jeudi 14 novembre 2013 08:56:46 Stephen Connolly a écrit :
> > > > > Hmmm... ok, I'll roll back and drop the staging repo
> > > > >
> > > > > On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr>
> >
> > wrote:
> > > > > > content staged here:
> > > > > > http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> > > > > >
> > > > > > notice I had to tweak m-changes-p version (done in trunk too) and
> >
> > fix
> >
> > > > > > manually
> > > > > > staging site siince the actual automatic location is wrong: I
> > > > > > still
> > > >
> > > > need
> > > >
> > > > > > to fix
> > > > > > trunk (see MSITE-687)
> > > > > >
> > > > > > I you can wait a little bit before re-rolling the release, I'll
> >
> > fix it
> >
> > > > > > tonight
> > > > > > (with compatibility with m-site-p 3.3- too)
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Hervé
> > > > > >
> > > > > > Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > > > > > > I suppose you did "mvn site-deploy"
> > > > > > > but for such a multi-module project, you need to use "mvn
> > > > > > > scm-publish:publish- scm" [1]
> > > > > > >
> > > > > > > Notice actual Doxia 1.5 can't be injected into maven-site-plugin
> > > >
> > > > because
> > > >
> > > > > > of
> > > > > >
> > > > > > > DOXIA-499 + DOXIASITETOOLS-85
> > > > > > > perhaps the class should be readded for compatibility, but
> > > > > > > marked
> > > > > > > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p
> > > >
> > > > release
> > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Hervé
> > > > > > >
> > > > > > > [1]
> >
> > http://maven.apache.org/developers/website/deploy-component-reference-docu
> >
> > > > > > m
> > > > > >
> > > > > > > entation.html
> > > > > > >
> > > > > > > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > > > > > > WARNING: Going to buffer response body of large or unknown
> >
> > size.
> >
> > > > Using
> > > >
> > > > > > > > getResponseBodyAsStream instead is recommended.
> >
> > > > > > > > [INFO] Downloading from JIRA at:
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> >
> > > > > > > > tu
> >
> > sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> >
> > > > > > > > 0&r eset=true&decorator=none
> > > > > > > >
> > > > > > > > [WARNING]
> > > > > > > >
> > > > > > > > org.apache.maven.plugin.MojoExecutionException: Failed to
> > > > > > > > parse
> > > >
> > > > JIRA
> > > >
> > > > > > XML.
> > > > > >
> > > > > > > > at
> > > > > > > > org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> >
> > > > > > > > at
> >
> > org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> >
> > > > > > > > ir aDownloader.java:753)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> >
> > > > > > > > at
> >
> > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> >
> > > > > > > > t. java:190)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> >
> > > > > > > > Do cumentRenderer.java:219)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> >
> > > > > > > > lt SiteRenderer.java:319)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> >
> > > > > > > > Re nderer.java:135)
> > > > > > > >
> > > > > > > > at
> >
> > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> >
> > > > > > > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Stephen Connolly <st...@gmail.com>.
On 14 November 2013 23:33, Hervé BOUTEMY <he...@free.fr> wrote:
> Le jeudi 14 novembre 2013 20:35:18 Stephen Connolly a écrit :
> > Cool. I'll give it a shot after getting some people to bed... Are the
> > instructions on
> > http://maven.apache.org/developers/release/maven-shared-release.htmlcorrect
> > w.r.t. Staging the doxia site, or is there some crazy-ass pub-sub
> > incantation I must invoke to stage the site?
> no, these instructions are not ok, mainly because Doxia is a multi-module
> project
> So you really have to follow [1]
> ie:
> 1. generate site
> 2. stage
> 3. invoke scm-publish explicitely (and not hidden in site-deploy phase)
>
scm-publish is dog slow... still transmitting the commit... after 45 minutes
>
> Regards,
>
> Hervé
>
>
> [1]
> http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
>
> >
> > On Thursday, 14 November 2013, Hervé BOUTEMY wrote:
> > > m-site-p configuration fixed
> > >
> > > and compatibility tested in dist-tool-plugin: see
> > > http://svn.apache.org/r1541998[1]
> > >
> > > we only need Markdown module, the incompatibility is in doxia-core
> only,
> > > but it's
> > > not a problem
> > >
> > > so ready for the new release :)
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 14 novembre 2013 08:56:46 Stephen Connolly a écrit :
> > > > Hmmm... ok, I'll roll back and drop the staging repo
> > > >
> > > > On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr>
> wrote:
> > > > > content staged here:
> > > > > http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> > > > >
> > > > > notice I had to tweak m-changes-p version (done in trunk too) and
> fix
> > > > > manually
> > > > > staging site siince the actual automatic location is wrong: I still
> > >
> > > need
> > >
> > > > > to fix
> > > > > trunk (see MSITE-687)
> > > > >
> > > > > I you can wait a little bit before re-rolling the release, I'll
> fix it
> > > > > tonight
> > > > > (with compatibility with m-site-p 3.3- too)
> > > > >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > > > > > I suppose you did "mvn site-deploy"
> > > > > > but for such a multi-module project, you need to use "mvn
> > > > > > scm-publish:publish- scm" [1]
> > > > > >
> > > > > > Notice actual Doxia 1.5 can't be injected into maven-site-plugin
> > >
> > > because
> > >
> > > > > of
> > > > >
> > > > > > DOXIA-499 + DOXIASITETOOLS-85
> > > > > > perhaps the class should be readded for compatibility, but marked
> > > > > > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p
> > >
> > > release
> > >
> > > > > > Regards,
> > > > > >
> > > > > > Hervé
> > > > > >
> > > > > > [1]
> > >
> > >
> http://maven.apache.org/developers/website/deploy-component-reference-docu
> > >
> > > > > m
> > > > >
> > > > > > entation.html
> > > > > >
> > > > > > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > > > > > WARNING: Going to buffer response body of large or unknown
> size.
> > >
> > > Using
> > >
> > > > > > > getResponseBodyAsStream instead is recommended.
> > >
> > > > > > > [INFO] Downloading from JIRA at:
> > >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> > >
> > > > > > > tu
> > >
> > >
> sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> > >
> > > > > > > 0&r eset=true&decorator=none
> > > > > > >
> > > > > > > [WARNING]
> > > > > > >
> > > > > > > org.apache.maven.plugin.MojoExecutionException: Failed to parse
> > >
> > > JIRA
> > >
> > > > > XML.
> > > > >
> > > > > > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > > > > > >
> > > > > > > at
> org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> > > > > > >
> > > > > > > at
> > >
> > >
> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> > >
> > > > > > > ir aDownloader.java:753)
> > > > > > >
> > > > > > > at
> > > > >
> > > > >
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> > > > >
> > > > > > > at
> > >
> > >
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> > >
> > > > > > > t. java:190)
> > > > > > >
> > > > > > > at
> > >
> > >
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> > >
> > > > > > > Do cumentRenderer.java:219)
> > > > > > >
> > > > > > > at
> > >
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> > >
> > > > > > > lt SiteRenderer.java:319)
> > > > > > >
> > > > > > > at
> > >
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> > >
> > > > > > > Re nderer.java:135)
> > > > > > >
> > > > > > > at
> > > > >
> > > > >
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> > > > >
> > > > > > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Hervé BOUTEMY <he...@free.fr>.
Le jeudi 14 novembre 2013 20:35:18 Stephen Connolly a écrit :
> Cool. I'll give it a shot after getting some people to bed... Are the
> instructions on
> http://maven.apache.org/developers/release/maven-shared-release.html correct
> w.r.t. Staging the doxia site, or is there some crazy-ass pub-sub
> incantation I must invoke to stage the site?
no, these instructions are not ok, mainly because Doxia is a multi-module
project
So you really have to follow [1]
ie:
1. generate site
2. stage
3. invoke scm-publish explicitely (and not hidden in site-deploy phase)
Regards,
Hervé
[1] http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
>
> On Thursday, 14 November 2013, Hervé BOUTEMY wrote:
> > m-site-p configuration fixed
> >
> > and compatibility tested in dist-tool-plugin: see
> > http://svn.apache.org/r1541998[1]
> >
> > we only need Markdown module, the incompatibility is in doxia-core only,
> > but it's
> > not a problem
> >
> > so ready for the new release :)
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 14 novembre 2013 08:56:46 Stephen Connolly a écrit :
> > > Hmmm... ok, I'll roll back and drop the staging repo
> > >
> > > On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr> wrote:
> > > > content staged here:
> > > > http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> > > >
> > > > notice I had to tweak m-changes-p version (done in trunk too) and fix
> > > > manually
> > > > staging site siince the actual automatic location is wrong: I still
> >
> > need
> >
> > > > to fix
> > > > trunk (see MSITE-687)
> > > >
> > > > I you can wait a little bit before re-rolling the release, I'll fix it
> > > > tonight
> > > > (with compatibility with m-site-p 3.3- too)
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > > > > I suppose you did "mvn site-deploy"
> > > > > but for such a multi-module project, you need to use "mvn
> > > > > scm-publish:publish- scm" [1]
> > > > >
> > > > > Notice actual Doxia 1.5 can't be injected into maven-site-plugin
> >
> > because
> >
> > > > of
> > > >
> > > > > DOXIA-499 + DOXIASITETOOLS-85
> > > > > perhaps the class should be readded for compatibility, but marked
> > > > > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p
> >
> > release
> >
> > > > > Regards,
> > > > >
> > > > > Hervé
> > > > >
> > > > > [1]
> >
> > http://maven.apache.org/developers/website/deploy-component-reference-docu
> >
> > > > m
> > > >
> > > > > entation.html
> > > > >
> > > > > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > > > > WARNING: Going to buffer response body of large or unknown size.
> >
> > Using
> >
> > > > > > getResponseBodyAsStream instead is recommended.
> >
> > > > > > [INFO] Downloading from JIRA at:
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> >
> > > > > > tu
> >
> > sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> >
> > > > > > 0&r eset=true&decorator=none
> > > > > >
> > > > > > [WARNING]
> > > > > >
> > > > > > org.apache.maven.plugin.MojoExecutionException: Failed to parse
> >
> > JIRA
> >
> > > > XML.
> > > >
> > > > > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > > > > >
> > > > > > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> > > > > >
> > > > > > at
> >
> > org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> >
> > > > > > ir aDownloader.java:753)
> > > > > >
> > > > > > at
> > > >
> > > > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> > > >
> > > > > > at
> >
> > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> >
> > > > > > t. java:190)
> > > > > >
> > > > > > at
> >
> > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> >
> > > > > > Do cumentRenderer.java:219)
> > > > > >
> > > > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> >
> > > > > > lt SiteRenderer.java:319)
> > > > > >
> > > > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> >
> > > > > > Re nderer.java:135)
> > > > > >
> > > > > > at
> > > >
> > > > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> > > >
> > > > > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Stephen Connolly <st...@gmail.com>.
Cool. I'll give it a shot after getting some people to bed... Are the
instructions on
http://maven.apache.org/developers/release/maven-shared-release.htmlcorrect
w.r.t. Staging the doxia site, or is there some crazy-ass pub-sub
incantation I must invoke to stage the site?
On Thursday, 14 November 2013, Hervé BOUTEMY wrote:
> m-site-p configuration fixed
>
> and compatibility tested in dist-tool-plugin: see
> http://svn.apache.org/r1541998[1]
>
> we only need Markdown module, the incompatibility is in doxia-core only,
> but it's
> not a problem
>
> so ready for the new release :)
>
> Regards,
>
> Hervé
>
> Le jeudi 14 novembre 2013 08:56:46 Stephen Connolly a écrit :
> > Hmmm... ok, I'll roll back and drop the staging repo
> >
> > On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr> wrote:
> > > content staged here:
> > > http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> > >
> > > notice I had to tweak m-changes-p version (done in trunk too) and fix
> > > manually
> > > staging site siince the actual automatic location is wrong: I still
> need
> > > to fix
> > > trunk (see MSITE-687)
> > >
> > > I you can wait a little bit before re-rolling the release, I'll fix it
> > > tonight
> > > (with compatibility with m-site-p 3.3- too)
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > > > I suppose you did "mvn site-deploy"
> > > > but for such a multi-module project, you need to use "mvn
> > > > scm-publish:publish- scm" [1]
> > > >
> > > > Notice actual Doxia 1.5 can't be injected into maven-site-plugin
> because
> > >
> > > of
> > >
> > > > DOXIA-499 + DOXIASITETOOLS-85
> > > > perhaps the class should be readded for compatibility, but marked
> > > > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p
> release
> > > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1]
> > >
> > >
> http://maven.apache.org/developers/website/deploy-component-reference-docu
> > > m
> > >
> > > > entation.html
> > > >
> > > > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > > > WARNING: Going to buffer response body of large or unknown size.
> Using
> > > > > getResponseBodyAsStream instead is recommended.
> > >
> > > > > [INFO] Downloading from JIRA at:
> > >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> > >
> > > > > tu
> > >
> > >
> sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> > >
> > > > > 0&r eset=true&decorator=none
> > > > >
> > > > > [WARNING]
> > > > >
> > > > > org.apache.maven.plugin.MojoExecutionException: Failed to parse
> JIRA
> > >
> > > XML.
> > >
> > > > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > > > >
> > > > > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> > > > >
> > > > > at
> > >
> > >
> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> > >
> > > > > ir aDownloader.java:753)
> > > > >
> > > > > at
> > >
> > > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> > >
> > > > > at
> > >
> > >
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> > >
> > > > > t. java:190)
> > > > >
> > > > > at
> > >
> > >
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> > >
> > > > > Do cumentRenderer.java:219)
> > > > >
> > > > > at
> > >
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> > >
> > > > > lt SiteRenderer.java:319)
> > > > >
> > > > > at
> > >
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> > >
> > > > > Re nderer.java:135)
> > > > >
> > > > > at
> > >
> > > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> > >
> > > > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.
--
Sent from my phone
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Hervé BOUTEMY <he...@free.fr>.
m-site-p configuration fixed
and compatibility tested in dist-tool-plugin: see http://svn.apache.org/r1541998[1]
we only need Markdown module, the incompatibility is in doxia-core only, but it's
not a problem
so ready for the new release :)
Regards,
Hervé
Le jeudi 14 novembre 2013 08:56:46 Stephen Connolly a écrit :
> Hmmm... ok, I'll roll back and drop the staging repo
>
> On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr> wrote:
> > content staged here:
> > http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
> >
> > notice I had to tweak m-changes-p version (done in trunk too) and fix
> > manually
> > staging site siince the actual automatic location is wrong: I still need
> > to fix
> > trunk (see MSITE-687)
> >
> > I you can wait a little bit before re-rolling the release, I'll fix it
> > tonight
> > (with compatibility with m-site-p 3.3- too)
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > > I suppose you did "mvn site-deploy"
> > > but for such a multi-module project, you need to use "mvn
> > > scm-publish:publish- scm" [1]
> > >
> > > Notice actual Doxia 1.5 can't be injected into maven-site-plugin because
> >
> > of
> >
> > > DOXIA-499 + DOXIASITETOOLS-85
> > > perhaps the class should be readded for compatibility, but marked
> > > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p release
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1]
> >
> > http://maven.apache.org/developers/website/deploy-component-reference-docu
> > m
> >
> > > entation.html
> > >
> > > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > > WARNING: Going to buffer response body of large or unknown size. Using
> > > > getResponseBodyAsStream instead is recommended.
> >
> > > > [INFO] Downloading from JIRA at:
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> >
> > > > tu
> >
> >
sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> >
> > > > 0&r eset=true&decorator=none
> > > >
> > > > [WARNING]
> > > >
> > > > org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA
> >
> > XML.
> >
> > > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > > >
> > > > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> > > >
> > > > at
> >
> > org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> >
> > > > ir aDownloader.java:753)
> > > >
> > > > at
> >
> > org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> >
> > > > at
> >
> >
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> >
> > > > t. java:190)
> > > >
> > > > at
> >
> >
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> >
> > > > Do cumentRenderer.java:219)
> > > >
> > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> >
> > > > lt SiteRenderer.java:319)
> > > >
> > > > at
> >
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> >
> > > > Re nderer.java:135)
> > > >
> > > > at
> >
> > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> >
> > > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> > > >
> > > > at
> >
> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild
> >
> > > > Pl uginManager.java:101)
> > > >
> > > > at
> >
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Stephen Connolly <st...@gmail.com>.
Hmmm... ok, I'll roll back and drop the staging repo
On 14 November 2013 07:12, Hervé BOUTEMY <he...@free.fr> wrote:
> content staged here:
> http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
>
> notice I had to tweak m-changes-p version (done in trunk too) and fix
> manually
> staging site siince the actual automatic location is wrong: I still need
> to fix
> trunk (see MSITE-687)
>
> I you can wait a little bit before re-rolling the release, I'll fix it
> tonight
> (with compatibility with m-site-p 3.3- too)
>
> Regards,
>
> Hervé
>
> Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> > I suppose you did "mvn site-deploy"
> > but for such a multi-module project, you need to use "mvn
> > scm-publish:publish- scm" [1]
> >
> > Notice actual Doxia 1.5 can't be injected into maven-site-plugin because
> of
> > DOXIA-499 + DOXIASITETOOLS-85
> > perhaps the class should be readded for compatibility, but marked
> > deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p release
> >
> > Regards,
> >
> > Hervé
> >
> > [1]
> >
> http://maven.apache.org/developers/website/deploy-component-reference-docum
> > entation.html
> > Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > > WARNING: Going to buffer response body of large or unknown size. Using
> > > getResponseBodyAsStream instead is recommended.
> > >
> > > [INFO] Downloading from JIRA at:
> > >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> > > tu
> > >
> sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> > > 0&r eset=true&decorator=none
> > >
> > > [WARNING]
> > >
> > > org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA
> XML.
> > >
> > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> > >
> > > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> > >
> > > at
> > >
> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> > > ir aDownloader.java:753)
> > >
> > > at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> > >
> > > at
> > >
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> > > t. java:190)
> > >
> > > at
> > >
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> > > Do cumentRenderer.java:219)
> > >
> > > at
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> > > lt SiteRenderer.java:319)
> > >
> > > at
> > >
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> > > Re nderer.java:135)
> > >
> > > at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> > >
> > > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> > >
> > > at
> > >
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild
> > > Pl uginManager.java:101)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > > :2 09)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > > :1 53)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > > :1 45)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
> > > fe cycleModuleBuilder.java:84)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
> > > fe cycleModuleBuilder.java:59)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(L
> > > if ecycleStarter.java:183)
> > >
> > > at
> > >
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStar
> > > te r.java:161)
> > >
> > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> > >
> > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> > >
> > > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> > >
> > > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> > >
> > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> > >
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >
> > > at
> > >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > > 57 )
> > >
> > > at
> > >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> > > pl .java:43)
> > >
> > > at java.lang.reflect.Method.invoke(Method.java:606)
> > >
> > > at
> > >
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.
> > > ja va:290)
> > >
> > > at
> > >
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230
> > > )
> > >
> > > at
> > >
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launche
> > > r. java:409)
> > >
> > > at
> > >
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> > >
> > > Caused by: org.xml.sax.SAXParseException; lineNumber: 117;
> columnNumber:
> > > 3;
> > > The element type "meta" must be terminated by the matching end-tag
> > > "</meta>".
> > >
> > > at
> > >
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> > > Source)
> > >
> > > at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
> Source)
> > >
> > > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> > >
> > > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> > >
> > > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> > >
> > > at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
> > >
> > > at
> > >
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unkno
> > > wn Source)
> > >
> > > at
> > >
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispa
> > > tc her.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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> > > Source)
> > >
> > > at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
> > >
> > > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
> > >
> > > ... 30 more
> > >
> > > [INFO]
> > >
> > > [INFO] --- maven-site-plugin:3.2:deploy (default-deploy) @ doxia ---
> > >
> > > [INFO] Parent project loaded from repository:
> > > org.apache.maven:maven-parent:pom:23
> > >
> > > [INFO] Parent project loaded from repository: org.apache:apache:pom:13
> > >
> > > [ERROR]
> > >
> > > Unsupported protocol: 'scm' for site deployment to
> > > distributionManagement.site.url=scm:svn:
> > > https://svn.apache.org/repos/infra/websites/production/maven/content/.
> > >
> > > Currently supported protocols are: http, file, https.
> > >
> > > Protocols may be added through wagon providers.
> > >
> > > For more information, see
> > >
> > >
> http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-p
> > > ro tocol.html
> > >
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> >
> > > [INFO] Reactor Summary:
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Hervé BOUTEMY <he...@free.fr>.
content staged here: http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/
notice I had to tweak m-changes-p version (done in trunk too) and fix manually
staging site siince the actual automatic location is wrong: I still need to fix
trunk (see MSITE-687)
I you can wait a little bit before re-rolling the release, I'll fix it tonight
(with compatibility with m-site-p 3.3- too)
Regards,
Hervé
Le jeudi 14 novembre 2013 01:40:37 Hervé BOUTEMY a écrit :
> I suppose you did "mvn site-deploy"
> but for such a multi-module project, you need to use "mvn
> scm-publish:publish- scm" [1]
>
> Notice actual Doxia 1.5 can't be injected into maven-site-plugin because of
> DOXIA-499 + DOXIASITETOOLS-85
> perhaps the class should be readded for compatibility, but marked
> deprecated, waiting for a new full Doxia+DoxiaSiteTools+m-site-p release
>
> Regards,
>
> Hervé
>
> [1]
> http://maven.apache.org/developers/website/deploy-component-reference-docum
> entation.html
> Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> > WARNING: Going to buffer response body of large or unknown size. Using
> > getResponseBodyAsStream instead is recommended.
> >
> > [INFO] Downloading from JIRA at:
> > http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&sta
> > tu
> > sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=100
> > 0&r eset=true&decorator=none
> >
> > [WARNING]
> >
> > org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
> >
> > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
> >
> > at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
> >
> > at
> > org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJ
> > ir aDownloader.java:753)
> >
> > at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
> >
> > at
> > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRepor
> > t. java:190)
> >
> > at
> > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Report
> > Do cumentRenderer.java:219)
> >
> > at
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defau
> > lt SiteRenderer.java:319)
> >
> > at
> > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSite
> > Re nderer.java:135)
> >
> > at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> >
> > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> >
> > at
> > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild
> > Pl uginManager.java:101)
> >
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > :2 09)
> >
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > :1 53)
> >
> > at
> > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java
> > :1 45)
> >
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
> > fe cycleModuleBuilder.java:84)
> >
> > at
> > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li
> > fe cycleModuleBuilder.java:59)
> >
> > at
> > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(L
> > if ecycleStarter.java:183)
> >
> > at
> > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStar
> > te r.java:161)
> >
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> >
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> >
> > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> >
> > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> >
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> >
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >
> > at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> > 57 )
> >
> > at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm
> > pl .java:43)
> >
> > at java.lang.reflect.Method.invoke(Method.java:606)
> >
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.
> > ja va:290)
> >
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230
> > )
> >
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launche
> > r. java:409)
> >
> > at
> > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> >
> > Caused by: org.xml.sax.SAXParseException; lineNumber: 117; columnNumber:
> > 3;
> > The element type "meta" must be terminated by the matching end-tag
> > "</meta>".
> >
> > at
> > org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> > Source)
> >
> > at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
> >
> > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> >
> > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> >
> > at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> >
> > at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
> >
> > at
> > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unkno
> > wn Source)
> >
> > at
> > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispa
> > tc her.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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> > Source)
> >
> > at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
> >
> > at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
> >
> > ... 30 more
> >
> > [INFO]
> >
> > [INFO] --- maven-site-plugin:3.2:deploy (default-deploy) @ doxia ---
> >
> > [INFO] Parent project loaded from repository:
> > org.apache.maven:maven-parent:pom:23
> >
> > [INFO] Parent project loaded from repository: org.apache:apache:pom:13
> >
> > [ERROR]
> >
> > Unsupported protocol: 'scm' for site deployment to
> > distributionManagement.site.url=scm:svn:
> > https://svn.apache.org/repos/infra/websites/production/maven/content/.
> >
> > Currently supported protocols are: http, file, https.
> >
> > Protocols may be added through wagon providers.
> >
> > For more information, see
> >
> > http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-p
> > ro tocol.html
> >
> > [INFO]
> > ------------------------------------------------------------------------
>
> > [INFO] Reactor Summary:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Can somebody (Hervé?) stage the Doxia 1.5 site
Posted by Hervé BOUTEMY <he...@free.fr>.
I suppose you did "mvn site-deploy"
but for such a multi-module project, you need to use "mvn scm-publish:publish-
scm" [1]
Notice actual Doxia 1.5 can't be injected into maven-site-plugin because of
DOXIA-499 + DOXIASITETOOLS-85
perhaps the class should be readded for compatibility, but marked deprecated,
waiting for a new full Doxia+DoxiaSiteTools+m-site-p release
Regards,
Hervé
[1] http://maven.apache.org/developers/website/deploy-component-reference-documentation.html
Le mercredi 13 novembre 2013 16:33:24 Stephen Connolly a écrit :
> WARNING: Going to buffer response body of large or unknown size. Using
> getResponseBodyAsStream instead is recommended.
>
> [INFO] Downloading from JIRA at:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&statu
> sIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=1000&r
> eset=true&decorator=none
>
> [WARNING]
>
> org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
>
> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
>
> at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108)
>
> at
> org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJir
> aDownloader.java:753)
>
> at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347)
>
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.
> java:190)
>
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDo
> cumentRenderer.java:219)
>
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Default
> SiteRenderer.java:319)
>
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRe
> nderer.java:135)
>
> at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPl
> uginManager.java:101)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:2
> 09)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:1
> 53)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:1
> 45)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
> cycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Life
> cycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Lif
> ecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarte
> r.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57
> )
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.ja
> va:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.
> java:409)
>
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>
> Caused by: org.xml.sax.SAXParseException; lineNumber: 117; columnNumber: 3;
> The element type "meta" must be terminated by the matching end-tag
> "</meta>".
>
> at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)
>
> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
>
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
>
> at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc
> her.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.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
>
> at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>
> at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:128)
>
> ... 30 more
>
> [INFO]
>
> [INFO] --- maven-site-plugin:3.2:deploy (default-deploy) @ doxia ---
>
> [INFO] Parent project loaded from repository:
> org.apache.maven:maven-parent:pom:23
>
> [INFO] Parent project loaded from repository: org.apache:apache:pom:13
>
> [ERROR]
>
> Unsupported protocol: 'scm' for site deployment to
> distributionManagement.site.url=scm:svn:
> https://svn.apache.org/repos/infra/websites/production/maven/content/.
>
> Currently supported protocols are: http, file, https.
>
> Protocols may be added through wagon providers.
>
> For more information, see
> http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-pro
> tocol.html
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Reactor Summary:
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org