Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-2531

Links for generated sites in Maven multi-module project are incorrect.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: PC, OS: Linux
    • Similar Issues:

      Description

      When Maven2 project is setup to generate the Maven site, Hudson displays
      'Maven-generated site' links on the project page. If the project is a
      multi-module Maven project then that link points to a site generated for one of
      the modules and not the project itself.
      Maven will generate the sites individually for every module but links between
      parent modules and child modules will only work after the site has been deployed
      or staged.
      As a suggestion, the 'Maven-generated site' link should point to that module's site.

        Attachments

          Issue Links

            Activity

            Hide
            abayer Andrew Bayer added a comment -

            Taking issue.

            Show
            abayer Andrew Bayer added a comment - Taking issue.
            Hide
            abayer Andrew Bayer added a comment -

            I think the Maven site integration with Hudson is pretty much unworkable - given
            a choice, I'd remove it completely. It just doesn't make sense in relation to
            Hudson. That said, if someone wants to write a plugin along the lines of what at
            mentions, feel free.

            Show
            abayer Andrew Bayer added a comment - I think the Maven site integration with Hudson is pretty much unworkable - given a choice, I'd remove it completely. It just doesn't make sense in relation to Hudson. That said, if someone wants to write a plugin along the lines of what at mentions, feel free.
            Hide
            cristalp cristalp added a comment -

            I think that Hudson should either
            a) ignore the Maven site completely (which would be a pity)

            or

            b) if it's not possible to handle multi-module sites correctly, at least be
            able to calculate the project's URL based on the site configuration of Maven

            Show
            cristalp cristalp added a comment - I think that Hudson should either a) ignore the Maven site completely (which would be a pity) or b) if it's not possible to handle multi-module sites correctly, at least be able to calculate the project's URL based on the site configuration of Maven
            Hide
            blidgey blidgey added a comment -

            I would vote for linking to the generated site URL, or at least making the option to link to the generated site URL or to the local copy. We deploy our sites to a server anyway, so the maven site stored inside Hudson is sort of irrelevant anyway.

            Show
            blidgey blidgey added a comment - I would vote for linking to the generated site URL, or at least making the option to link to the generated site URL or to the local copy. We deploy our sites to a server anyway, so the maven site stored inside Hudson is sort of irrelevant anyway.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in hudson
            User: : mfriedenhagen
            Path:
            trunk/hudson/main/maven-plugin/src/main/java/hudson/maven/reporters/MavenSiteArchiver.java
            trunk/hudson/main/test/src/test/java/hudson/maven/MavenProjectTest.java
            trunk/hudson/main/test/src/test/resources/hudson/maven/maven-multimodule-site.zip
            http://jenkins-ci.org/commit/28369
            Log:
            Fixed JENKINS-2531 by storing sites for multimodule projects.
            Simple projects with one POM will find the site directly beneath

            {@code site}.
            For multi module projects the project whose pom is referenced in the configuration (i.e. the {@link MavenBuild#getParentBuild()} will be recorded to
            the {@code site}

            directory, module projects' sites will be stored beneath {@code site/${moduleProject.artifactId}}.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mfriedenhagen Path: trunk/hudson/main/maven-plugin/src/main/java/hudson/maven/reporters/MavenSiteArchiver.java trunk/hudson/main/test/src/test/java/hudson/maven/MavenProjectTest.java trunk/hudson/main/test/src/test/resources/hudson/maven/maven-multimodule-site.zip http://jenkins-ci.org/commit/28369 Log: Fixed JENKINS-2531 by storing sites for multimodule projects. Simple projects with one POM will find the site directly beneath {@code site}. For multi module projects the project whose pom is referenced in the configuration (i.e. the {@link MavenBuild#getParentBuild()} will be recorded to the {@code site} directory, module projects' sites will be stored beneath {@code site/${moduleProject.artifactId}}.

              People

              • Assignee:
                mfriedenhagen Mirko Friedenhagen
                Reporter:
                at at
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: