[
https://issues.apache.org/jira/browse/MAHOUT-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020091#comment-14020091
]
Dmitriy Lyubimov commented on MAHOUT-1562:
------------------------------------------
I think the best way is to tweak spark and math-scala module to generate scala
docs by default (just needs to add goal to scala plugin). that change wouldn't
require any jenkins changes.
Suppose that's done, my Jenkins knowledge betrays me. there's only one
directory avaialble to publish with "publish javadocs" goal, and currently it
publishes javadocs for mrlegacy module. Not sure how to make it publish all
javadocs and all scaladocs. Tried to use wildcards there, but it complains that
wildcards are not allowed. Weird. How do the Jenkins designer assume one should
publish docs for a project with multiple modules? or the assumption is that
we'd add a separate build for every module just to do that?
> Publish Scaladocs
> -----------------
>
> Key: MAHOUT-1562
> URL: https://issues.apache.org/jira/browse/MAHOUT-1562
> Project: Mahout
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 0.9
> Reporter: Pat Ferrel
> Priority: Minor
> Labels: scaladocs
> Fix For: 1.0
>
>
> The poms that relate to Scala have the maven-scala-plugin, which will
> generate Scaladocs if you navigate to the scala subproject and run
> mvn scala:doc
> They will appear in target/site/scaladocs for the subproject.
> This is not supported from the parent mahout pom
> This should be incorporated into the process that publishes the javadocs. It
> appears the Scala code is not publically browsable as Scaladocs. Not sure
> where this process lives but the scala stuff should probably follow that same
> pattern/process as javadocs
--
This message was sent by Atlassian JIRA
(v6.2#6252)
