Closed gkop closed 13 years ago
I've updated the documentation here: c6fb0469d669e50667453827d75b220f50a667f3.
The current behavior is expected ... and isn't even a part of Jammit at all. In Rails, some of your environments have caching enabled, and some do not. If you're running in an environment with caching enabled, dynamic assets will be cached; if not, not.
The docs http://documentcloud.github.com/jammit/ are inaccurate regarding 0.6.0.
Problems with this statement a) jammit does not package assets in test environment b) jammit does not cache assets that it packages on-demand
Both of these behaviors described in the docs but missing from the gem seem like sensible defaults to me.
I put this query out on #documentcloud and did not find an answer as to how the gem is supposed to behave or why.