Uploaded image for project: 'Maven Shared Components'
  1. Maven Shared Components
  2. MSHARED-480

use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: maven-reporting-impl 2.4
    • Fix Version/s: None
    • Component/s: maven-reporting-impl
    • Labels:
      None

      Description

      currently, when a reporting mojo is not used as maven-site-plugin's report but as direct mojo invocation, maven-site-renderer default skin is always used: would be more consistent if using site decoration consistently with maven-site-plugin
      Or more precisely, I didn't currently find any reporting plugin that did the effort to mimic maven-site-plugin's decoration model/skin: every reporting plugin I know of uses features of maven-reporting-impl for site rendring (with this known limitation)

      implementing the feature in maven-reporting-impl will make it accessible to any reporting plugin once it upgrades it dependency version

      once done, we can activate skin resources copy, that was commented while working on MSHARED-120 (and would not give expected result if skin used is not consistent)

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              hboutemy Herve Boutemy

              Dates

              • Created:
                Updated:

                Issue deployment