Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Mon, 16 Sep 2013 17:54:59 +0000 (UTC)
From: "Lenny Primak (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: <JIRA.12668823.1379354098567.141013.1379354099496@arcas>
In-Reply-To: <JIRA.12668823.1379354098567@arcas>
References: <JIRA.12668823.1379354098567@arcas>
Subject: [jira] [Created] (TAP5-2185) Problem with the asset checksums and
 relative paths based on them
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Lenny Primak created TAP5-2185:
----------------------------------

             Summary: 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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira