mercredi 23 avril 2014

theme package build generate a non-debug CSS file that imports debug CSS files

We've created a theme package for a theme that extends the Neptune theme.

When we build the theme using Cmd 4.0.4.84, the resulting CSS is split into several component parts with a numeric suffix, so Cmd creates a 'master' CSS that imports each of the component files. The non-debug version of the master CSS file, though, imports the debug versions of the component parts.

For example, for a theme named 'myneptune' the debug CSS files would be:


myneptune-all-debug.css

myneptune-all-debug_01.css

myneptune-all-debug_02.css


The content of myneptune-all-debug.css is


Code:



@import 'myneptune-all-debug_01.css';
@import 'myneptune-all-debug_02.css';

Cmd then creates these non-debug files:

myneptune-all.css

myneptune-all_01.css

myneptune-all_02.css


but the content of myneptune-all.css is


Code:



@import 'myneptune-all-debug_01.css';@import 'myneptune-all-debug_02.css';

So the main non-debug CSS file is really just a minified version of the debug CSS file.

Looking at the Ant build scripts, this looks to be resulting from the following in the '-compile-css' target in 'sass-impl.xml':



Code:




<x-compress-css-files
dir="${build.resources.dir}"
prefix="${build.all.css.debug.prefix}"
outprefix="${build.all.css.prefix}"/>

That call looks like it simply minifies any CSS file that includes '<package>-all-debug' in its name.

This looks like it might be a Cmd bug.


Has anyone seen this before and come up with a workaround that generates a non-debug CSS file that imports the non-debug components?





Aucun commentaire:

Enregistrer un commentaire