Ok. Fixed and deploying (ed). On 4/15/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Only the ContextAssetFactory. Looks like spec libraries might be getting resolved by invoking that factory directly instead of using AssetSource to do it - which makes sense now that I know what is happening. I'll hunt down the culprit and "fix em" for good. The old style "/net/sf/tacos/Tacos.library" should be working whether it's in the context or classpath if AssetSource was being used. BTW The asset resolutions work very well now...Having to say "context:" or "classpath:" should be rare corner cases where specifity is needed as it'll figure it out on it's own. (no matter if the definition is at the class or spec level) On 4/15/07, Andreas Andreou <[EMAIL PROTECTED]> wrote: > > I think i know what's happening - at least here's what i've just > observed: > > I used to have in my .application files stuff like > <library id="tacos" specification-path="/net/sf/tacos/Tacos.library"/> > > This NO longer works, one has to do > <library id="tacos" > specification-path="classpath:/net/sf/tacos/Tacos.library"/> > > Do the recent changes assume context location by default then? > Should we keep the old way working? > > > On 4/15/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > Yep, probably related to something I did today. I'd suggest you pick a > > > more > > specific version to get over your issues until they can be looked at: > > > > > > > http://people.apache.org/repo/m2-snapshot-repository/org/apache/tapestry/tapestry-framework/maven-metadata.xml > > > > (p.s. I don't see the root of your stack, maybe it's obvious when > looking > > at > > spec parser but I wanted to be sure. ) I might need more specific > > information as library finding works fine for me currently using > tapestry > > "as is". > > > > On 4/15/07, Patrick Moore < [EMAIL PROTECTED]> wrote: > > > > > > a new snapshot was pushed today ... still having the same > problem.... > > > > > > On 4/14/07, Patrick Moore < [EMAIL PROTECTED]> wrote: > > > > > > > > Hi there -- > > > > > > > > I seem to be having problems with the latest 4.1.2 snapshot > finding > > > child > > > > libraries. The snapshot is failing to find Dojo.library in tacos. > > > > > > > > > > > > Stack Trace: > > > > > > > > - org.apache.tapestry.parse.SpecificationParser.parseDocument( > > > > SpecificationParser.java:1645) > > > > <snipped> > > > > > > > > > > > -- > > Jesse Kuhnert > > Tapestry/Dojo team member/developer > > > > Open source based consulting work centered around > > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > > > > > -- > Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr > Tapestry / Tacos developer > Open Source / JEE Consulting > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
