I'm having this same issue with Jenkins 1.446 and Maven 3.0.3. I have found that if I set up the Jenkins job to run "mvn deploy site", then the Maven generated site link is broke and I need to append the artifactId to the URL. I also notice in the jobs/job_name/site directory that there is an artifactId subdirectory and the site contents are in there rather than in the site directory.
However, if I run "mvn package deploy", the Maven generated site link works just fine. Furthermore, all of the files that previously appeared in jobs/job_name/site/artifactId now appear in jobs/job_name/site.
I checked the workspace/job_name/site directory in both cases, and both times the site files, including index.html, were generated in that directory.
Jenkins copies the site files from workspace/job_name/site, so why, with the exact same mvn pom.xml, doing the same build, does Jenkins in one case copy the generated site to one location, and in the other case copies the site to a different location?
So I disagree very much with evernat - there is an index.html file, it was generated in both cases. The behavior points to a Jenkins problem.
We're seeing this (or something very similar) too, with Hudson 1.358 on Windows.
Here's an example URL generated by Hudson:
http://sthinfra06:8080/job/apcore-main/site/?
What it should say is one of:
http://sthinfra06:8080/job/apcore-main/site/apcore
http://sthinfra06:8080/job/apcore-main/site/apcore/
"apcore-main" is the Hudson job name.
"apcore" is the Maven artifact ID for this project.
Hudson is installed in d:\hudson, and the on-disk path to the generated site is d:\hudson\jobs\apcore-main\site\apcore.