JIRAs created:
https://issues.apache.org/jira/browse/TAP5-2167
https://issues.apache.org/jira/browse/TAP5-2168
On Sep 5, 2013, at 9:30 PM, Howard Lewis Ship wrote:
> You can leave the asset in the old location, and Tapestry will find it,
> with a warning.
>
> Or you can move it to the new locat
Will port JIRA shortly...
the 5.3 location warning is actually an error, and it should be made into a
warning though
It's really annoying because it appears SEVERE red in the logs
thanks!
On Sep 5, 2013, at 9:30 PM, Howard Lewis Ship wrote:
> You can leave the asset in the old location, and Tape
You can leave the asset in the old location, and Tapestry will find it,
with a warning.
Or you can move it to the new location; /assets/LIB-NAME/path.js ... the
LIB-NAME is determined from the library containing the component.
The error message only reports the 5.3 location; it should be updat
Now I understand how I could get so confused:
The error message is this:
targetException
org.apache.tapestry5.ioc.internal.OperationException: Unable to locate asset
'classpath:com/flowlogix/web/mixins/js/DateFieldParserPatch.js' (the file does
not exist).
But, I have to put the asset here:
MET
(answering my own question)
Looks like the semantics have changed. Used to be that assets were looked up
relative to class package name,
now they are just looked up relative to root.
On Sep 5, 2013, at 6:37 PM, Lenny Primak wrote:
> I am trying to migrate FlowLogix library to T5.4...
> There ar
I am trying to migrate FlowLogix library to T5.4...
There are a whole bunch of mixins there, that use JavaScript
@Import(library="xxx.js").
I used to have those .js in the classpath in the same package.
Now, with the new packaging scheme, I moved them to META-INF/assets/flowlogix.
After this, none
