You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2013/11/28 09:01:40 UTC
[jira] [Commented] (TAP5-1871) Tapestry should warn when a page
imports the same asset via multiple JavaScriptStacks
[ https://issues.apache.org/jira/browse/TAP5-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834583#comment-13834583 ]
Jochen Kemnade commented on TAP5-1871:
--------------------------------------
5.4 introduces the same issue for modules
> Tapestry should warn when a page imports the same asset via multiple JavaScriptStacks
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1871
> URL: https://issues.apache.org/jira/browse/TAP5-1871
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.2, 5.3.3
> Reporter: Jochen Kemnade
> Priority: Minor
> Labels: patch, test-patch
> Attachments: 0001-Throw-an-exception-if-an-asset-is-to-be-added-to-a-s.patch
>
>
> When an asset is used in multiple stacks and a page imports those stacks, the asset is added to the page and - for JS assets - executed multiple times. It would be nice if Tapestry would detect this kind of "misconfiguration" and throw an exception or at least log a warning.
--
This message was sent by Atlassian JIRA
(v6.1#6144)