You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/12/22 01:43:13 UTC
[jira] [Commented] (TAP5-2034) When the application operates with a
context path, asset URLs are incorrectly formed
[ https://issues.apache.org/jira/browse/TAP5-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538585#comment-13538585 ]
Hudson commented on TAP5-2034:
------------------------------
Integrated in tapestry-trunk-freestyle #981 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/981/])
TAP5-2034: When the application operates with a context path, asset URLs are incorrectly formed (Revision 116ca802e21c65175051d6d18adfe2871faa06b8)
Result = FAILURE
hlship :
Files :
* tapestry-core/src/main/java/org/apache/tapestry5/internal/services/assets/AssetPathConstructorImpl.java
* tapestry-core/src/test/java/org/apache/tapestry5/internal/services/ContextAssetFactoryTest.java
> When the application operates with a context path, asset URLs are incorrectly formed
> ------------------------------------------------------------------------------------
>
> Key: TAP5-2034
> URL: https://issues.apache.org/jira/browse/TAP5-2034
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Matías Blasi
> Assignee: Howard M. Lewis Ship
> Labels: assets, js, rewrite
> Fix For: 5.4
>
>
> When trying 5.4-alpha-1 from 5.4-js-rewrite branch, I'm getting the following error when trying to browse a recently created webapp (with mvn archetype:generate)
> bootstrap.css: comexassets/1.0-SNAPSHOT-DEV/meta/tapestry5/bootstrap_2_1_1/css
> "comex" is my context root, and the assets folder is added with no slash separator.
> Note: I started with a working tapestry-5.3.6 application, created with maven archetype plugin, and later I built tapestry-5.4-alpha-1 from sources, and updated the pom' dependencies.
> I know that 5.4-alpha-1 is not stable, but I didn't find this issue in jira, I think that it is something to fix.
> Regards,
> Matías.
--
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