Uploaded image for project: 'Maven Site Plugin'
  1. Maven Site Plugin
  2. MSITE-786

Migrating from 3.4 to 3.5.1, a mvn site run now ask me for 'META-INF/maven/site.vm'

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.5.1
    • 3.6
    • None
    • None

    Description

      When I switched from 3.4 to 3.5.1, running mvn site now spits errors like :

      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project api-parent: Could not find the site decoration template 'META-INF/maven/site.vm': Encountered "1.0" at META-INF/maven/site.vm"
      

      Ok, seems like it's a new requirement, so I copied the one provided on https://svn.apache.org/repos/asf/maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/resources/org/apache/maven/doxia/siterenderer/resources/default-site.vm, as proposed by https://maven.apache.org/plugins/maven-site-plugin/examples/creatingskins.html.

      The thing is that I would have expected this file to be optionnal (everything works fine with 3.4).

      But it's not enough : as the default-site-macros.vm has been separated from the site.vm file, we get an error because it's missing. There is no place on the maven-site site that tells the user where to find this file (I had to fetch it from the svn repo...).

      Once that was done (copying the default-site-macros.vm in the root directory of my project), I ran mvn site once more and I get an error :

      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project api-i18n: Template file '/Users/elecharny/apacheds/trunks/shared/target/checkout/maven-site.vm' does not exist -> [Help 1]
      

      actually, api-i18n is a subproject - I have 50 of them -. And the problem is that the so called 'missing template' actually exists ! :

      localhost:checkout elecharny$ ll /Users/elecharny/apacheds/trunks/shared/target/checkout/maven-site.vm
      -rw-r--r--  1 elecharny  staff  3466 Oct 26 10:56 /Users/elecharny/apacheds/trunks/shared/target/checkout/maven-site.vm
      

      All in all, the only solution I have at the moment is to rollback to 3.4. The ideal fix would be to have the default templates to be embedded into the plugin, and not required to be present on disk...

      Attachments

        Issue Links

          Activity

            People

              hboutemy Herve Boutemy
              elecharny Emmanuel Lécharny
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: