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 <[email protected]> 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
