[jira] [Closed] (ARCHETYPE-688) Incompatibities with Velocity in Archetypes

["Slawomir Jaranowski (Jira)" <ji...@apache.org>]

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

Slawomir Jaranowski closed ARCHETYPE-688.
-----------------------------------------
    Resolution: Fixed

> Incompatibities with Velocity in Archetypes
> -------------------------------------------
>
>                 Key: ARCHETYPE-688
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-688
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Archetypes, Generator, Plugin
>    Affects Versions: 3.3.0
>            Reporter: Javid
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.3.1
>
>
> Hello, 
> I am having an issue caused by the new version of the maven-archetype-plugin:3.3.0 related with the recent upgrade of velocity 1.7 to velocity 2.3.
> As it is reported in the [Velocity configuration|https://velocity.apache.org/engine/2.3/upgrading.html#vtl-changes_1], from version 1.7 to version 2+, the use of hyphens have changed and now they are not supported in parameters, causing errors.
> To avoid this, there is a property that allow backwards compatibility [detailed here|https://velocity.apache.org/engine/2.3/configuration.html#backward-compatibility], but I believe there is no way to tell maven-archetype-plugin to allow this compatibility in the configuration.
> I have a very complex project that uses hyphens in multiple instances and now, it is impossible to generate a project with the new archetype:3.3.0 version.
> My problem is that changing the hyphen will cause a major impact in some other projects that rely on this archetype, so it is not a viable option for me to do.
> Could it be possible for you to include a way to modify Velocity configuration in maven-archetype-plugin:3.3.0? This would be extremely helpful so we can keep up with the future updates
> Thanks in advance!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)