You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2014/07/01 23:22:27 UTC
[jira] [Assigned] (TAP5-2185) Problem with the asset checksums and
relative paths based on them
[ https://issues.apache.org/jira/browse/TAP5-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiago H. de Paula Figueiredo reassigned TAP5-2185:
---------------------------------------------------
Assignee: Thiago H. de Paula Figueiredo
> Problem with the asset checksums and relative paths based on them
> -----------------------------------------------------------------
>
> Key: TAP5-2185
> URL: https://issues.apache.org/jira/browse/TAP5-2185
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Lenny Primak
> Assignee: Thiago H. de Paula Figueiredo
>
> When JavaScript modules reference other (non-tapestry) JS code via relative paths,
> or absolute paths that have to be configured, the checksum is preventing
> the other resources from being accessed properly
> Discussion regarding this can be found here:
> http://apache-tapestry-mailing-list-archives.1045711.n5.nabble.com/Re-5-4-Problems-with-the-asset-checksums-and-relative-paths-based-on-them-td5723366.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)