i add following exclusions and everything works fine.
org.apache.struts
struts2-spring-plugin
${struts.version}
spring-context
org.springframework
On 12/9/07, DM <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've been following along with the tutorial, but whenver I run the tests or
> try to deploy the application I'm getting the following error:
>
> ---
> testHandleRequest(org.appfuse.webapp.controller.PersonC
Depends on where maven is putting your repository but will be under
something like:
c:\documents and settings\\.m2\org\appfuse\tapestry\2.0.1\...
(Sorry doing from memory here - not near my dev machine)
On Dec 10, 2007 7:42 AM, Daniel Kibler <[EMAIL PROTECTED]> wrote:
>
> Karl - What is the p
Hi Michael,
Michael Horwitz wrote:
Whenever I have had to do something like this I resort to using Joda
time (http://joda-time.sf.net) in my model classes. Way easier
date/time manipulation, and makes this sort of thing a little easier
if you can do it in code. Extra incentive for us is th
Hi,
I've been following along with the tutorial, but whenver I run the tests or try
to deploy the application I'm getting the following error:
---
testHandleRequest(org.appfuse.webapp.controller.PersonControllerTest) Time
elapsed: 3.437 sec <<< ERROR!
Karl - What is the path to the jar?
Karl Laird-2 wrote:
>
> Also have this issue - but with the Tapestry project; same as Daniel did a
> 2.0 to 2.0.1 upgrade.
>
> Adding the jar manually to the Eclipse build path worked for me
> eventually...
>
>
>
--
View this message in context:
http:
Also have this issue - but with the Tapestry project; same as Daniel did a
2.0 to 2.0.1 upgrade.
Adding the jar manually to the Eclipse build path worked for me
eventually...
On Dec 10, 2007 7:01 AM, Daniel Kibler <[EMAIL PROTECTED]> wrote:
>
> I'm having this same issue, but with Eclipse, s
In the main pom I changed the following property (at the very bottom).
1.2.1
Previously it had been set to 1.2.2
I've been doing some testing and haven't noticed any adverse affects from
reverting to this dbcp version. Then did a 'mvn clean package'. BTW I'm using
full source so not sure if
I'm having this same issue, but with Eclipse, since upgrading from 2.0 to
2.0.1. I run maven from the command line but my action classes show syntax
errors and won't compile in Eclipse. My action tests when run from the
command line fail too.
Is there a way to get this package back in the claspa
