[
https://issues.jenkins-ci.org/browse/JENKINS-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162194#comment-162194
]
Peter Johnson commented on JENKINS-6681:
----------------------------------------
I spent some time looking into this problem and found out that Jenkins looks to
see if the site's index file is at <location-of-pom>/target/site/index.html. If
it is, then the generated site link works as expected for a regular (not
multi-module) Maven build. If the index file is not located there, then Jenkins
assumes that it is doing a multi-module build and thus it prefixes the
artifactId to the path for the site; thus each module within the multi-module
build can have its own site with the master module providing a main index page
with links to the individual module's sites. In the case of our builds, one of
the Maven plugins moved the POM (to target/pom.xml) and this plugin was invoked
just before the install phase. Once we corrected this (we configured the plugin
to update the POM in place), the generated site link now works again. So from
my point of view, this problem is solved for me, no fix is necessary. I hope my
analysis helps others.
> Maven-generated site link gives 404
> -----------------------------------
>
> Key: JENKINS-6681
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6681
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Affects Versions: current
> Reporter: adico
>
> After running goals "clean install site" in a Maven2 build, project home page
> shows a link called "Maven-generated site". This links gives a 404 because it
> is missing project-info.html off the end of the URL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
