Bram,
Thanks for the confirmation. Strangely, the problem in intermittent. But
since tomcat is the only variable that is changing, I hesitate to blame
maven. Still, if I have time, I may try maven 3x to see if that makes any
difference.
Cheers!
Bill
On Sat, Dec 7, 2013 at 4:23 AM, Bram
You might want to try
Apache-ant-1.8.4
Apache-maven-3.1.1
Apache-tomcat-7.0.47
together; no problem here with those here (did have a problem only
update Apache-tomcat).
--
Sponsored by Intel(R) XDK
Develop,
Tentatively, it looks as if upgrading to maven 3.3.1 is working... I was
hesitant to *downgrade* to ant 1.8.4, but a simple maven upgrade may have
done the trick. I did have to run mvn clean first, and followed it up with
mvn package and ant update.
I don't want to declare victory just yet,
Hi Bill,
we have seen exactly the same behaviour in the infrastructure of one of our
clients this week e.g.:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/oai]]
Caused by: java.lang.IllegalStateException:
Thanks Brian!
I'm still not clear on what this means -- wrong version of Maven? I'm
using:
Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
On Fri, Dec 6, 2013 at 2:03 PM, Brian Freels-Stendel bfre...@unm.eduwrote:
Hi Bill,
This looks like a jaxen conflict between maven and
, December 06, 2013 2:36 PM
To: Brian Freels-Stendel; dspace-tech
Subject: Re: [Dspace-tech] dspace and tomcat 7.0.47
Thanks Brian!
I'm still not clear on what this means -- wrong version of Maven? I'm using:
Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500)
On Fri, Dec 6, 2013 at 2:03 PM
6 matches
Mail list logo
