Fixed. David H. DeWolf wrote:
Yes, this is a known issue. We need to exclude some of the transient dependencies in the pom of the webapps. It's in jira but I just haven't gotten around to it yet. There was a post on the maven list the other day that looks like we need to do. If anyone is interested in submitting a patch, try to do something like the following:<dependency> <groupId>springframework< /groupId> <artifactId>spring-hibernate</artifactId> <version>1.2.5</version> <scope>compile</scope> <exclusions> <exclusion> <groupId>org.hibernate</groupId> <artifactId>hibernate-annotations</artifactId> </exclusion> <exclusion> <groupId>org.hibernate</groupId> artifactId>hibernate</artifactId> </exclusion> </exclusions> </dependency> DavidOn 10/26/05, *Stefan Armbruster* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:Hi, I just tried to get started with Pluto 1.1. Following the README the Portal and Testsuite were deployed into a fresh Tomcat 5.5.9. When accessing http://localhost:8080/pluto/portal <http://localhost:8080/pluto/portal>, I got an exception: Failed to load or instantiate TagLibraryValidator class: org.apache.taglibs.standard.tlv.JstlCoreTLV Google got the answer: http://ryandaigle.com/pebble/2005/01/27/1106856324774.html In short, after removing the jsp-api.jar from both webapps' WEB-INF/lib directory the page displays fine. jsp-api.jar is already available in tomcat's common/lib. The version inside the war files seems to be another version. I could not find any reference in the sources to jsp-api.jar. How can this be removed in the sources? Regards, Stefan
