Per your request, issue filed: https://issues.apache.org/jira/browse/TAP5-1353
Adam
On Mon, Nov 22, 2010 at 2:29 PM, Adam Zimowski wrote:
> Will do and agreed.
>
> On Mon, Nov 22, 2010 at 2:19 PM, Howard Lewis Ship wrote:
>> Please add an issue, but I don't see this as a blocker for Tapestry 5.
Will do and agreed.
On Mon, Nov 22, 2010 at 2:19 PM, Howard Lewis Ship wrote:
> Please add an issue, but I don't see this as a blocker for Tapestry 5.2.
>
> On Mon, Nov 22, 2010 at 11:48 AM, Adam Zimowski wrote:
>
>> Thank You Howard ! Yes, I moved the file to subfolder "resources",
>> changed my
Please add an issue, but I don't see this as a blocker for Tapestry 5.2.
On Mon, Nov 22, 2010 at 11:48 AM, Adam Zimowski wrote:
> Thank You Howard ! Yes, I moved the file to subfolder "resources",
> changed my annotation to:
>
> @Import(library="classpath:/resources/util.js")
>
> Modified the mod
Thank You Howard ! Yes, I moved the file to subfolder "resources",
changed my annotation to:
@Import(library="classpath:/resources/util.js")
Modified the module:
configuration.add("js", "resources");
And Viola ! Works. I guess I exercised extreme scenario :)
Adam
On Mon, Nov 22, 2010 at 1:04
Looks like a bug; you should move around the assets to deeper folders, that
should solve the problem. Alternate, the ClasspathAssetManager should
reject your contribution ... you really should package these things deeper,
somewhere inside your library or applications' root package; that was the
in
Minor typo... I also had a stylesheet which is inconsequential to this
and I removed it from the e-mail. The import really is:
@Import(library="classpath:util.js")
Adam
On Mon, Nov 22, 2010 at 11:13 AM, Adam Zimowski wrote:
> Hi,
>
> In my component class I have:
>
> @Import(stylesheet="library
