cssImport preprocessor mangling order of information in resulting file

[GoogleCodeExporter]

The cssImport preprocessor is processing all of the import statements then 
appending the remaining CSS content (comments and other css constructs) to the 
end of the file.

Unfortunately this reordering is affecting a media query that I have in my less 
source which will be included before some custom additional less directives.

Attached to this issue is a small maven project using the 1.6.3-SNAPSHOT of 
wro4j-maven-plugin (based on 6127ae74ca327d63e24eefb5649da61a40a8e2e9).

I have replaced the original comments with lorem ipsum paragraphs and removed 
references to my actual less files.

The result of the cssImport run shows that all of the imports are replaced 
properly but the comments are all moved to the end of the file.

The project I'm on is requiring a media query that is embedded in the main less 
file to be at the location it is listed in the source.

Is there any way to alter this behavior to replace the import inline, including 
any additional imports, at the point of detection?

Original issue reported on code.google.com by djgraff...@gmail.com on 1 Feb 2013 at 1:46

Attachments:

• lesswebapp-2a84443.zip

[GoogleCodeExporter]

And before I forget - the project is currently also using lesscss-maven-plugin 
and the 1.3.3 version of less.

I have been advised to try the rhino based processor to see if it would make a 
difference. At this time I have not tried this.

Original comment by djgraff...@gmail.com on 1 Feb 2013 at 1:47

[GoogleCodeExporter]

The cssImport processor expects all the @import statements to be located on top 
of the css file. This is an expected behavior.

Closing issue with WONTFIX resolution.

Original comment by alex.obj...@gmail.com on 6 Feb 2013 at 5:10

• Changed state: WontFix