maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <>
Subject [jira] [Commented] (MSITE-786) Migrating from 3.4 to 3.5.1, a mvn site run now ask me for 'META-INF/maven/site.vm'
Date Fri, 28 Oct 2016 14:49:58 GMT


Hervé Boutemy commented on MSITE-786:

Hi Emmanuel,

Maven Site Plugin 3.5 upgraded to Velocity 1.7, where Velocity 1.5 was used before: there
are some Velocity compatibility issues
For example, there is

You have 2 options:
- either fix Velocity 1.7 compatibility
- either force Velocity 1.5, if you don't have time to upgrade your skin for now: see

See you soon in Seville :)

> Migrating from 3.4 to 3.5.1, a mvn site run now ask me for  'META-INF/maven/site.vm'
> ------------------------------------------------------------------------------------
>                 Key: MSITE-786
>                 URL:
>             Project: Maven Site Plugin
>          Issue Type: Bug
>    Affects Versions: 3.5.1
>         Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M;
support was removed in 8.0
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_60, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.5", arch: "x86_64", family: "mac"
>            Reporter: Emmanuel Lecharny
> When I switched from 3.4 to 3.5.1, running {{mvn site}} now spits errors like :
> {noformat}
> [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"
> {noformat}
> Ok, seems like it's a new requirement, so I copied the one provided on,
as proposed by
> 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 :
> {noformat}
> [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]
> {noformat}
> actually, {{api-i18n}} is a subproject - I have 50 of them -. And the problem is that
the so called 'missing template' actually exists ! :
> {noformat}
> 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
> {noformat}
> 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...

This message was sent by Atlassian JIRA

View raw message