[
https://jira.codehaus.org/browse/MOJO-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293972#comment-293972
]
Marcel Overdijk commented on MOJO-1816:
---------------------------------------
Hi Christopher,
Could you share your setup?
Which version of less css maven plugin used and your pom.xml configuration for
the plugin.
Basically the plugin/compiler is cheking for this:
{code}
public void compile(LessSource input, File output, boolean force) throws
IOException, LessException {
if (force || !output.exists() || output.lastModified() <
input.getLastModifiedIncludingImports()) {
String data = compile(input);
FileUtils.writeStringToFile(output, data, encoding);
}
}
{code}
Where input.getLastModifiedIncludingImports() is the last modified timestamp of
the LESS file itself or of any of its imports.
Force should also be false by default btw.
> lesscss-maven-plugin: optimise compilation step
> -----------------------------------------------
>
> Key: MOJO-1816
> URL: https://jira.codehaus.org/browse/MOJO-1816
> Project: Mojo
> Issue Type: Bug
> Reporter: Christopher Hunt
> Assignee: Marcel Overdijk
>
> When using the plugin, it appears to be invoked every time I perform my
> process-resources goal. Given that the LESS compilation is very time
> consuming (seconds given Bootstrap and 3 other files), it would be great if
> the plugin only activated when files (or their dependencies) actually change.
> The best way to achieve this is IMHO is to compare the modification time of a
> target file to its source file. In addition the target file must be examined
> to see if it depends on files, and the same check must be applied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
