...
[11:16:31 CDT(-0500)] <EricDalquist> means that it is only really controlable via a jvm level property
[11:16:47 CDT(-0500)] <EricDalquist> I suppose someone could write code that took the portal.properties value
[11:16:57 CDT(-0500)] <EricDalquist> and did a System.setProperty on JVM startup
[11:17:07 CDT(-0500)] <EricDalquist> but the ultimate control needs to be a JVM property
[11:18:46 CDT(-0500)] <b-sure> makes sense. I just think it would be convenient for me as the app admin if I didn't need to get the web admins involved to set it when the portal is deployed. Maybe I'll just add it as a customization for now.
[11:19:11 CDT(-0500)] <EricDalquist> just curious
[11:19:17 CDT(-0500)] <EricDalquist> why are you deploying with this set to false?
[11:20:33 CDT(-0500)] <b-sure> well we are still in fine tuning of the theme/css but need to do some wider scale testing on a 3node cluseter. So our load balancer sticks me on only 1 of the three nodes and I'm not able to adjust the other nodes easily.
[11:21:06 CDT(-0500)] <b-sure> we will definately use the aggregation in production.
[11:21:14 CDT(-0500)] <EricDalquist> ah ok
[11:21:16 CDT(-0500)] <EricDalquist> just making sure
[11:21:33 CDT(-0500)] <EricDalquist> as the unaggregated CSS/JS ends up being quite a bit of content 
[11:21:39 CDT(-0500)] <EricDalquist> with no caching
[11:21:48 CDT(-0500)] <b-sure> yeah