Try running with -e to get more info, the error message seems
misleading. Also try to clear your local cache, that sometimes helps.
Can you run the war:webapp goal by itself?
-Lukas
[EMAIL PROTECTED] wrote:
Hi Lukas,
Now I changed to the latest (and last) version of the codeczar tomcat plugin,
maven-tomcat-plugin.1.2.1.jar, which I got from this url:
http://www.codeczar.com/maven/codeczar-tomcat/plugins/maven-tomcat-plugin-1.2.1.jar
I've read here:
http://masterdev.dyndns.dk/dev/14.html
That in order to properly use it, you had to update to Tomcat 5.5.12, which I also did.
Now when calling maven tomcat:deploy
It gives me this error:
test:test:
war:webapp:
-------------------------------------------------------------------------------
Unable to obtain goal [war:webapp]
Error parsing project.xml
'MY_MAVEN_HOME\cache\maven-java-plugin-1.6.1\project.xml'
com.bea.xml.stream.MXParserFactory
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
This is all really weird, plz help.
Thanks in advance,
Christine
-------- Original-Nachricht --------
Datum: Thu, 20 Dec 2007 10:48:07 +0100
Von: Lukas Theussl <[EMAIL PROTECTED]>
An: Maven Users List <users@maven.apache.org>
Betreff: Re: Maven 1.1 + tomcat plugin
Hi,
[EMAIL PROTECTED] wrote:
Hi,
I just updated from Maven 1.0.2 to Maven 1.1. In Maven 1.02 I used
the tomcat plugin from codezar: maven-tomcat-plugin-1.1.jar. Using
Maven 1.1, I typed in: maven tomcat:deploy
This gave me the error:
-------------------------------------------------------------------------------
Error parsing project.xml
'MAVEN-HOME\cache\maven-tomcat-plugin-1.1\project.xml'
ParseError at [row,col]:[44,11] Message: Unrecognised tag: 'id'
As noted on the compat page
(http://maven.apache.org/maven-1.x/reference/backwards-compatibility.html),
Maven 1.1 is much less tolerant of invalid project.xml files, so this
plugin seems to be broken in m11.
-------------------------------------------------------------------------------
So I went to the codezar website and updated the maven dependency to
version 1.2.
However, now, when calling maven tomcat:deploy
-------------------------------------------------------------------------------
Where did you get this plugin version? The link we have on our plugins
page (http://www.codeczar.com/products/maven-tomcat-plugin/) is not
valid anymore.
Unable to obtain goal [tomcat:_jspc]
org.apache.jasper.JasperException:
file:MY-SOURCE-FOLDER/MY_JSP_FILE.jsp(1,1) The absolute uri: http
://jakarta.apache.org/struts/tags-tiles cannot be resolved in either
web.xml or the jar files deployed with this application file:MY-SOURCE-
FOLDER/MY_JSP_FILE.jsp(1,1) The absolute uri:http://jakarta.apache.org/
struts/tags-tiles cannot be resolved in either web.xml or the jar
files deployed with this application
-------------------------------------------------------------------------------
BUILD FAILED
Can't help you with this one (at least they fixed the plugin pom... :)
), but a quick google search suggests that it's a more general problem,
not maven related.
The file it complains about just contains the tag library definitions:
<%@ taglib prefix="tiles"
uri="http://jakarta.apache.org/struts/tags-tiles"; %>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt"; %>
<%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions"; %>
The URI http://jakarta.apache.org/struts/tags-tiles doesn't exist
anymore, have they moved somewhere else?
I did some research on Google, and found out this error could have
something to do with servlet api 2.3 vs 2.4 - however as far as I know
I am using 2.4 in my web.xml.
Any ideas what's wrong, and what I could do to fix it? (I am not
allowed to move to Maven2, and I was told it wasn't so good anyway)
Damn right! :p
Cheers,
-Lukas
Thanks in advance,
Christine
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
