If you do a
cvs update -d
it should create the new "org.dom4j.xpp" package/directory for you, then it
should all compile OK. When doing a cvs update without the -d, no new
directories are created, so new packages don't get downloaded.
The xpp package is definitely in CVS
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dom4j/dom4j/src/java/org/dom4
j/xpp/
James
----- Original Message -----
From: "Thomas Nichols" <[EMAIL PROTECTED]>
To: "James Strachan" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, December 21, 2001 4:04 PM
Subject: CVS build failure
> Hi James,
> I'm getting the following on a build after a CVS update:
>
> compile:
> [javac] Compiling 206 source files to
/usr/local/java/dom4j/build/classes
> [javac]
> /usr/local/java/dom4j/build/src/org/dom4j/io/XPPReader.java:31: Class
> org.dom4j.xpp.ProxyXmlStartTag not found in import.
> [javac] import org.dom4j.xpp.ProxyXmlStartTag;
>
>
> I can't find org.dom4j.xpp.* -- and changing it in XPPReader.java to
import
> org.gjt.xpp.ProxyXmlStartTag doesn't fix it, even though PullParser2.jar
> has this class apparently available. Should I have both PullParser11 and
> PullParser2 in my lib dir?
>
> Any advice welcome -- I'm actually tracking a weird problem with
namespaces
> - element.getAttributeValue(QName) sometimes returns the correct result
and
> sometimes doesn't - so I tried refreshing CVS. Will restore my pre-update
> backup for now.
>
> Thanks,
> Thomas.
> Platform: Linux-Mandrake 7.2
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-dev