As we don't publish Mahout site (yet) so that last successful build execution site remains active even after failure(s), javadoc report is accessible through that Jenkins link only when Mahout-Quality build job is successful. It turns out that Mahout0Quality build job last execution has failed, hence javadoc link is broken. One can see that build job status at https://builds.apache.org/job/Mahout-Quality/ As master Yoda would say, "be patient we must", until build is successful again, or we start publishing site report.
As another alternative, one can generate javadoc locally with: mvn clean package -DskipTests=true javadoc:javadoc and then open from local filesystem mahout/core/target/site/apidocs/index.html Darius, similarly to previous time you reported broken wiki link, valid URL is: https://cwiki.apache.org/confluence/display/MAHOUT/Mahout+Wiki#MahoutWiki-Examples I'm not sure yet what (maybe some Confluence upgrade, or something else related) has in the past caused duplication of URLs. Anyway, take a look at the two broken and two corresponding valid URLs, I'm sure you'll notice the pattern. To find valid one, one can also just google mahout wiki page name (e.g. mahout wiki examples), search hits will have valid URLs. Kind regards, Stevo Slavic. On Tue, Aug 27, 2013 at 1:22 PM, Darius Miliauskas < [email protected]> wrote: > Dear All, > > ant the links from Wiki do not work as well: > https://cwiki.apache.org/MAHOUT/mahout-wiki.html#MahoutWiki-Examples > > > Best Wishes, > > Darius > > > 2013/8/27 Darius Miliauskas <[email protected]> > > > Dear All, > > > > that's absolutely true, Rafal! I almost wanted to write the same. > > Moreover, some links in "http://mahout.apache.org/"; are not working as > > well. Guys, I do not know who is responsible for the site but the site is > > the first face of the project. So, it would be nice if you spend some > hours > > just to make the site properly function, and in some places more > > understandable. It is more important than new functionalities in the new > > release because everybody judge you from the first impression. I already > > wrote that the instruction how to install, and run is very messy. I > managed > > to install but I spend almost a day to understand what was written there. > > README.txt file is not also very helpful. What a waste while the good > > instruction would make only half an hour, and mahout more attractive! > Just > > write a page instead of giving the links, and make the project look more > > attractive and substantial. You should revise the instructions, and make > it > > more simple for the ordinary user. > > > > > > Best Wishes, > > > > Darius > > > > > > 2013/8/27 Rafal Lukawiecki <[email protected]> > > > >> Dear All, > >> > >> The Javadoc for Mahout usually available on > >> http://builds.apache.org/job/Mahout-Quality/javadoc/ and linked to from > >> Jenkins at http://builds.apache.org/job/Mahout-Quality/ is showing > error > >> 404 at the moment. > >> > >> Rafal > >> > >> -- > >> > >> Rafal Lukawiecki > >> > >> Strategic Consultant and Director > >> > >> Project Botticelli Ltd > >> > >> > > >
