You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2019/05/27 07:24:00 UTC

[jira] [Resolved] (WICKET-6670) Minified resources and JavaScript compression don't play well together

     [ https://issues.apache.org/jira/browse/WICKET-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-6670.
-------------------------------------
    Resolution: Duplicate

> Minified resources and JavaScript compression don't play well together
> ----------------------------------------------------------------------
>
>                 Key: WICKET-6670
>                 URL: https://issues.apache.org/jira/browse/WICKET-6670
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 8.4.0
>            Reporter: Thomas Heigl
>            Priority: Major
>         Attachments: myproject.zip
>
>
> I switched my application from on-the-fly compression of resources to minifying resources during the Maven build.
> Previously, I had {{useMinifiedResources}} disabled. When I enabled the flag, I noticed that Wicket correctly serves the minified resource, *but* still compresses the original JS.
> This makes no sense to me.
> The behavior can be reproduced with the attached quickstart. Just open the homepage and check the error logs. The compressor is called for the unminified resource although Wicket serves the minified version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)