You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Florent ANDRE (Commented) (JIRA)" <ji...@apache.org> on 2012/01/07 18:11:40 UTC

[jira] [Commented] (CLEREZZA-536) Update online documentation

    [ https://issues.apache.org/jira/browse/CLEREZZA-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182031#comment-13182031 ] 

Florent ANDRE commented on CLEREZZA-536:
----------------------------------------

Here comes the long story ! :)

Now clerezza-site fail to each commit [1].

According to MSITE-490 [2] this is due to an outdated version of maven-site plugin.
As I don't know the version of maven on the build machine, I upgrade to 2.2 but if the mvn on build machine if >2.2.0 we can upgrade plugin version to 3.0 and be ready for mvn3 [3]...

Solving this issue raise another one [4] cause by Clirr plug-in in trunk/parent/slf4j-scala-api/.
I try some configuration of Clirr but get nothing working on it.... so I choose to remove it for the good of the build.

Looking at this pom (slf4j-scala-api), I find strange that the parent's of this module is slf4j's one and not zz's one... and that is status may be the cause of CLEREZZA-590.

So I change the parent of this module, remove this module in zz parent's <dependency> and add the slf4j-scala dep anywhere required.

Try mvn clean install and the mvn site and finaly working !
Just a last point here, site generation is long (on my machine due to laptop hard disk IMO), but also required a lot of memory (I front some out of memory before change mvn xmx)... have to see if it pass on the build machine...

Mvn result of site is :
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 96 minutes 36 seconds
[INFO] Finished at: Fri Jan 06 18:52:57 CET 2012
[INFO] Final Memory: 927M/1345M

----

[1] for example : https://builds.apache.org/job/clerezza-site/399/console
[2] http://jira.codehaus.org/browse/MSITE-490
[3] read introduction : http://maven.apache.org/plugins/maven-site-plugin/
[4] java.lang.NegativeArraySizeException
	at org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:660)
	at org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:263)
	at org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:243)
	at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:219)
	at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:355)
	at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
	at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
	at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
	at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
	at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
	at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
                
> Update online documentation
> ---------------------------
>
>                 Key: CLEREZZA-536
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-536
>             Project: Clerezza
>          Issue Type: Bug
>            Reporter: Florent ANDRE
>
> For example https://issues.apache.org/jira/browse/CLEREZZA-234 was applied, but not visible here http://incubator.apache.org/clerezza/mvn-site/org.apache.clerezza.rdf.core/documentation/tutorial_1.xhtml
> Fresh online documentation will be nice to have.
> Thanks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira