[
https://issues.apache.org/jira/browse/TAP5-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048303#comment-14048303
]
Howard M. Lewis Ship commented on TAP5-2139:
--------------------------------------------
The challenge is meshing these requirements with those concerning minimization
of stacks.
I'm going to research what it would take to mark an entire stack as
non-minimizable; this would allow assets to be isolated from minimization
effectively.
> When an exception occurs during minification, the asset should be sent
> unminimized
> ----------------------------------------------------------------------------------
>
> Key: TAP5-2139
> URL: https://issues.apache.org/jira/browse/TAP5-2139
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-webresources
> Affects Versions: 5.4
> Reporter: Jochen Kemnade
> Assignee: Howard M. Lewis Ship
>
> The current closure compiler version fails to minimize angular.js
> (https://github.com/angular/angular.js/issues/1304). A WroRuntimeException is
> thrown from GoogleClosureCompressorProcessor which is not handled, so the
> asset is not sent to the client at all.
> When an asset cannot be minimized for whatever reason, Tapestry should just
> send the original asset.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
