[ http://jira.codehaus.org/browse/MOJO-453?page=comments#action_79225 ]
Anagnostopoulos Kostis commented on MOJO-453:
---------------------------------------------
Very nice, the updToDate is indeed a plugin-wide issue.
Though personally, i would preffer the default expression
${maven.xml.forceCreation}, since (i think) this is an unspoken convention
among several maven plugins to preffix their variables with 'maven.', to avoid
conflicts with other cmd-line arguments
(or alternatively, ${maven.xml.forceTransform} unless there is a convention
for the 'forceCreation' part).
Regards,
Kostis
> [xml-maven-plugin] Perform up-to-date check, to avoid re-transforming files
> ---------------------------------------------------------------------------
>
> Key: MOJO-453
> URL: http://jira.codehaus.org/browse/MOJO-453
> Project: Mojo
> Issue Type: Improvement
> Components: xml
> Environment: version: 0.0.1
> svn revision: 2089
> Reporter: Anagnostopoulos Kostis
> Assigned To: Jochen Wiedmann
> Attachments: xmlplgn.upToDateChk-MOJO-453.patch,
> xmlplgn.upToDateChk-MOJO-453.patch
>
>
> The plugin does not test whether the result files of the 'transform' goal are
> up-to-date, and avoid re-processing them. This is necessary since ussually
> XSLT transformations take a long time to complete (i.e. in forked lifecycles,
> the delay is important).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
