Hello, OK, so this may be another dumb question (to follow up on my dumb question from a while ago). I appreciate your forbearance with all of these. The "deploy-war" seems to make use of the theme and skin files from inside uportal-war/target/…, and move those to the tomcat directory. I have generally been working inside uportal-war/src/… up until this point. So, I am wondering: - am I working in the wrong place and was supposed to be in /target all along? - if not, is there some other task that I am supposed to run first that (perhaps among other things) moves the stuff inside /src to /target? - if not, what exactly is supposed to be my workflow? Do I just copy the files from src to target after I am done with them, and then run the deploy task?
(Sorry, I'm just not very familiar with java and the directory structures are sort of making my head spin.) I'd been using some "directInject" build targets (from earlier on this list) to do skin development up until now, which copied the relevant files from uportal-war/src directly into tomcat. So, I haven't run into this yet. But now I am just trying to test the deployment and make sure that I understand the aggregation thing, and so I'm running into it. Thanks a lot, Jerry From: Eric Dalquist <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Fri, 22 Oct 2010 12:39:26 -0400 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [uportal-dev] Question about CSS aggregation You have to re-run the "ant deploy-war" task. Those aggregate files are generated at built time by a maven plugin based on the files listed in the skin.xml file. -Eric On 10/21/10 3:40 PM, Jerry Shipman wrote: Hello, I apologize if this is a dumb question… I am working on a “theme” and “skin” for uPortal 3.2. Following some of the advice from earlier in this list, I have disabled various different kinds of caching and am using someone’s “css.directInject” and “xsl.directInject” build targets to help me along. However, I am now running into a problem that is related to CSS aggregation. I think the short form of my question is: how can I get it to refresh the ‘aggregated’ css file (e.g. ...\media\skins\{theme}\{skin}\uportal3_4_A1EE8CC33EF9FD029156F29D9870130E.aggr.min.css ) for a given skin? The behavior I am seeing is: when css/js aggregation is enabled, I am seeing “old”, out-of-date CSS. When I disable it, I see my current CSS. This persists through server restarts and everything. I think that I need to get it to rebuild the aggregated file, but I don’t know how to do that. I think I tried re-enabling the caching and restarting, but it didn’t do the trick. Any ideas? I notice that the aggregated file is named “uportal3_...”, which is not the name of my skin. Is that a hint that I have something configured incorrectly? Thank you very much! Jerry -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
