[jira] [Closed] (SIS-112) Maven site on Jenkins has broken links

["Martin Desruisseaux (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SIS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Desruisseaux closed SIS-112.
-----------------------------------


> Maven site on Jenkins has broken links
> --------------------------------------
>
>                 Key: SIS-112
>                 URL: https://issues.apache.org/jira/browse/SIS-112
>             Project: Spatial Information Systems
>          Issue Type: Bug
>          Components: Build process
>    Affects Versions: 0.3
>         Environment: Jenkins
>            Reporter: Martin Desruisseaux
>            Assignee: Martin Desruisseaux
>             Fix For: 0.4
>
>
> Jenkins automatically generates a link toward the Maven generated site, which is available there:
> http://builds.apache.org/job/sis-trunk/site/
> However, in my understanding of {{JENKINS-6681}}, Jenkins does not use the {{mvn site:deploy}} goal for that purpose. Instead, it performs its own deployment (or simulates a deployment). Unfortunately sub-modules seem to have broken links. Our directory hierarchy is:
> {noformat}
> root
> ├── core
> │   ├── sis-utility
> │   ├── sis-metadata
> │   └── sis-referencing
> ├── storage
> │   ├── sis-storage
> │   └── sis-netcdf
> ...etc...
> {noformat}
> but Jenkins flattened everything like below:
> {noformat}
> root
> ├── core
> ├── sis-utility
> ├── sis-metadata
> ├── sis-referencing
> ├── storage
> ├── sis-storage
> ├── sis-netcdf
> ...etc...
> {noformat}
> Consequently there is no way to reach any {{sis-*}} module from the links created by Maven. This issue seems to be related to the following discussion:
> * http://issues.jenkins-ci.org/browse/JENKINS-6681
> As a workaround, we could deploy the site on some server using the standard {{mvn site:deploy}} goal. But which server?



--
This message was sent by Atlassian JIRA
(v6.2#6252)