OK, its the old plugin issue.
Since we changed a template resource (j2-seed.xml), we need to
explicitly go through the two step process
If you run "mvn -P tomcat" the first time, it uses the old plugin
resources
(1) mvn
(2) mvn -P tomcat
That fixed it for me
On Feb 6, 2007, at 1:32 PM, Timony, Michael wrote:
Reboot, redeployed, restarted everything and now it's working. Maybe
there I had stale DB connections? Next I'm going to try with WebSphere
6.1 & Oracle.
David: I haven't seen that error message in my builds.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
