You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by bu...@apache.org on 2004/02/20 09:37:02 UTC
DO NOT REPLY [Bug 27101] New: -
Unable to deploy portlet due to old Tomcat home variable name
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27101>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27101
Unable to deploy portlet due to old Tomcat home variable name
Summary: Unable to deploy portlet due to old Tomcat home variable
name
Product: Pluto
Version: Current CVS
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: general
AssignedTo: pluto-dev@jakarta.apache.org
ReportedBy: kweiner@unicon.net
When trying to deploy a portlet from the jakarta-pluto/deploy directory, I got
the following error:
[java] CASTOR-Exception: java.io.FileNotFoundException:
\webapps\pluto\WEB-INF\data\xml\portletdefinitionmapping.xml (The system cannot
find the path specified)
[java] java.io.IOException: Failed to load mapping file
/webapps\pluto\WEB-INF\data\xml\portletdefinitionmapping.xml
[java] at org.apache.pluto.portalImpl.Deploy.prepareWebArchive(Deploy.java:179)
[java] at org.apache.pluto.portalImpl.Deploy.main(Deploy.java:519)
This occurs because the Tomcat directory should be in the classpath, and my
build.properties sets "maven.tomcat.home" rather than "tomcat.home.pluto" as
specified in the deploy goal of jakarta-pluto/deploy/maven.xml
To be consistent with other maven.xml's in the project, I think the
deploy/maven.xml should be updated with the newer name for the Tomcat home
directory variable.