This probably related to the controversial fix for https://issues.apache.org/jira/browse/TAP5-815 that now protects classpath assets.
The problem you encountered (and similar) is also the reason why 5.1.0.6 and 5.1.0.7 releases were voted down I'm not 100% sure when the ultimate fix will be available (or how it'll tackle things) but for now the idea is that you have to whitelist the classpath resources you want to make available. Perhaps you just pulled in a new version of tapx-datefield that whitelists its own resources In any case, take a look at the net panel of firebug to make sure you don't have any unexpected 404. On Wed, Jan 27, 2010 at 03:45, Bryan Lewis <jbryanle...@gmail.com> wrote: > Okay, I tried it again. The maven update worked this time. It picked up > the new build with the -3 suffix. > > However, now I'm getting an error on one of my pages that contains the > tapx-datefield component, A javascript error pops up in a Blackbird > console: > > Tapestry.Initializer.tapxDateField() does not exist. > > I saw this once before after an update, and kicking/restarting things fixed > it. This time I've tried a clean build, updating Maven dependencies in > eclipse, building outside eclipse, restarting eclipse, clearing my browser > cache... it's not going away. Any ideas what would cause this? > > > On Tue, Jan 26, 2010 at 7:50 PM, Andreas Andreou <andy...@di.uoa.gr> wrote: > >> I'm not sure why you both have problems with 5.1.0.8-SNAPSHOT >> >> I see the correct files at: >> >> http://repository.apache.org/snapshots/org/apache/tapestry/tapestry-core/5.1.0.8-SNAPSHOT/ >> >> http://repository.apache.org/snapshots/org/apache/tapestry/tapestry-upload/5.1.0.8-SNAPSHOT/ >> >> Is it possible to investigate this some more? >> I remember i had manually deployed 5.1.0.7-SNAPSHOT, but >> 5.1.0.8-SNAPSHOT is auto-deployed from apache's hudson CI server, see: >> http://hudson.zones.apache.org/hudson/job/tapestry-5.1-freestyle/ >> http://twitter.com/tapestry_builds >> >> On Wed, Jan 27, 2010 at 01:23, David Rees <dree...@gmail.com> wrote: >> > On Tue, Jan 26, 2010 at 4:43 AM, Andreas Andreou <andy...@di.uoa.gr> >> wrote: >> >> I'm not sure how this is possible... Version ranges were supposed to >> help >> >> in that regard, i.e. you'd have your pom depend on Tapestry [5.1, 5.2) >> >> and perhaps this will just work for you >> > >> > Thanks for the suggestion. For now, I'll lock it to 5.1.0.8-SNAPSHOT. >> > >> > I noticed that tapestry-upload doesn't appear to to have any 5.1.0 >> > SHAPSHOT builds - is that expected or an oversight? >> > >> > Thanks! >> > >> > Dave >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> > For additional commands, e-mail: users-h...@tapestry.apache.org >> > >> > >> >> >> >> -- >> Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr >> Tapestry / Tacos developer >> Open Source / JEE Consulting >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
