Sorry this took so long.

I've attached a patched to #14108 that creates a resource from the @imports which allows them to be built into single files.

Still outstanding though is that the background images do not resolve. There is code in the optimizeCss transform to do it, but it always points to the original dojo location, not to the build location, so I don't think it works and I can't figure out how it is intended to work. Also, iirc, the old build tool collected all the images used and put them in a new folder. Relatedly, I haven't been able to get any of my custom code app images to move (I even tried targeting them with a package). I usually have an img folder in my css folder, and it does not copy over; I tried adding "css/img":1 into the copyOnly function in my profile which did not work.

Mike Wilcox
mike at

On Oct 20, 2011, at 10:34 PM, Rawld Gill wrote:
On Thursday, October 20, 2011 08:37:25 AM Mike Wilcox wrote:
I can confirm the css build bugs, and talked to Rawld about them last week
(he sounded extraordinarily busy btw). The fix to combine the files is not
too hard (I have a fix, but it may be more of a hack) -
could you post to the ticket. I'll review and commit.
but the fix to
resolve the background-image urls does not look easy, and the mechanism for
gathering the images into a "built" folder is no where to be found
Could you explain more. If the background image is in the source tree, it's
copied and is available to copy someplace else.


dojo-contributors mailing list
dojo-contributors at

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 13 of 18 | next ›
Discussion Overview
groupdojo-contributors @
postedOct 17, '11 at 3:10p
activeOct 24, '11 at 3:02p



site design / logo © 2022 Grokbase