Theming styles overhaul
(MGNLUI-704)
|
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | design |
| Affects Version/s: | None |
| Fix Version/s: | 5.0 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Samuli Penttilä | Assignee: | Samuli Penttilä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Sprint: | Iteration 2013-12, Iteration 2013-13, Iteration 2013-14, Iteration 2013-15 | ||||||||
| Description |
|
Sass compilation needs to be done before making deployment packages. Add a Maven goal to automate this. Please note that this is a production setup, perhaps a profile for CI. For development we still intend to use on-the-fly compilation |
| Comments |
| Comment by Mikaël Geljić [ 07/Mar/13 ] |
|
Compilation of 3rd party styles is actually in the responsibility of that module, in other words, we don't compile 3rd party styles into our theme, they're injected when starting an app instead. The scope of this issue is only for our own theme. |
| Comment by Samuli Penttilä [ 11/Mar/13 ] |
|
changed the static sass compilation so that it will publish compilation results only through widgetset package. After moving it to the gwt-compile-production profile I encountered problems with maven cleaning my compilation results when it did compilation in-place. |