[ 
https://issues.jenkins-ci.org/browse/JENKINS-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159727#comment-159727
 ] 

Peter Johnson commented on JENKINS-6681:
----------------------------------------

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 place 
the generated site in one location, and in the other case place the site in a 
different location?

So I disagree very much with evernat - there is an index.html file, it was 
generated in both cases. The behavior point to a Jenkins problem.
                
> 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

        

Reply via email to