OK, it's obviously not really the one I just fixed but it looks somewhat
similar. Maybe the order of Enhancement-/Injection-Workers for the
spring/other stuff (which I unfortunately don't use) is also defined
incompletely.
2007/9/20, mraible <[EMAIL PROTECTED]>:
>
>
> It happens for me on OS X an
It happens for me on OS X and the original problem was reported by someone on
Windows XP.
Matt
Marcus Schulte wrote:
>
> might be somehow related to
> https://issues.apache.org/jira/browse/TAPESTRY-1721 ... I'm looking into
> it.
> Which OS/jvm are you running?
>
> 2007/9/20, mraible <[EMAIL
might be somehow related to
https://issues.apache.org/jira/browse/TAPESTRY-1721 ... I'm looking into it.
Which OS/jvm are you running?
2007/9/20, mraible <[EMAIL PROTECTED]>:
>
>
> Any idea why Tapestry 4.1.3 works with jetty:run-war and tomcat:run (two
> Maven plugins), but not jetty:run? We're h
Any idea why Tapestry 4.1.3 works with jetty:run-war and tomcat:run (two
Maven plugins), but not jetty:run? We're having this problem in AppFuse 2.0.
http://www.nabble.com/Problem-with-jetty%3Arun-in-Tapestry-basic-archetype-tf4485474s2369.html#a12791114
Thanks,
Matt
--
View this message in co
