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/02 17:46:25 UTC

[jira] [Resolved] (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 resolved TAP5-2185.
-------------------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4

Solved by trying to find the asset in the classpath and in the context and, if found, redirect to its correct URL (the one with the correct checksum).

> 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
>              Labels: month-of-tapestry
>             Fix For: 5.4
>
>
> 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)