You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/08/08 10:28:00 UTC
[jira] [Resolved] (SLING-10696) HTL Maven Plugin: Switch default
phase to something prior compile
[ https://issues.apache.org/jira/browse/SLING-10696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-10696.
-------------------------------------
Fix Version/s: HTL Maven Plugin 2.0.4-1.4.0
Resolution: Fixed
Fixed in https://github.com/apache/sling-htl-maven-plugin/commit/233560ada6b761814bd3801041d3bdcfbbcadd7c
> HTL Maven Plugin: Switch default phase to something prior compile
> -----------------------------------------------------------------
>
> Key: SLING-10696
> URL: https://issues.apache.org/jira/browse/SLING-10696
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: HTL Maven Plugin 2.0.2-1.4.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: HTL Maven Plugin 2.0.4-1.4.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The mojo validate is used to optionally precompile HTL scripts into Java sources. As that steps requires a subsequent compilation via maven-compiler-plugin which is bound to phase "compile" as well, the default phase of "validate" should rather be a phase prior "compile" to make sure that the m-c-p:compile is always executed afterwards.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)