Since we are using the concatenated CSS files to load a skin on a page, and it seems the most convenient way to do it (instead of loading each component's individual CSS file), it doesn't matter much where the individual CSS files are placed. Currently, these individual files are being generated and placed inside each component's resource library (e.g. for slider we are creating 'sam' and 'rime' directories inside 'resources/org.icefaces.component.sliderentry', and each of them contains the CSS file(s) for that component, for that skin).

So, I thought that we could place all these generated individual files under the same (generated, not in the repository) resource library, maybe in 'org.icefaces.component.skins'. The advantage of this could be that it wouldn't be necessary to specify the resource library for each skin in the build script, potentially reducing the number of necessary lines to add a skin to just one (instead of 3). After all, all component-specific skin resources are now inside the component's source directory, so component developers only need to be concerned about that location, and the build script takes care of everything else, which is something that we wanted from the beginning.

Also, it would be better to use the '/build' directory inside '/component' to place all the temporary files and staging directories of the skin resources build process, instead of '/tools/smartsprites'.