> > > DId you got my logs? ( off-list ) > > > > I did. I deleted my maven repository (eheh.. I > > renamed) to force redownload, > > and did a clean rebuild. "BUILD SUCCESSFUL" > > Well, zapping repository did not help. Then it must > be xml parser issue... Shall we ad explicit > dependency to XML parser? > ( it is uncool to demand CLASSPATH, and even linux > people shall be able to get consistent build... ) > > I recall you know jelly pretty well - which parser you > are recommending?
I verified the following. I had xerces and xml-apis in classpath because of maven. ... C:\Java\maven-1.0.2\lib\endorsed\xerces-2.4.0.jar;C:\Java\maven-1.0.2\lib\en dorsed\xml-apis-1.0.b2.jar; .... Maybe linux maven distro don't have those jars. My first belief was that I've seen dependencies for these in project.xml, but I was mistaken. From commons-jelly's project.xml... (There they are ...eheh) http://svn.apache.org/viewcvs.cgi/jakarta/commons/proper/jelly/trunk/jelly-t ags/tag-project.xml?view=markup We see <dependency> <id>xml-apis</id> <version>1.0.b2</version> </dependency> And <dependency> <id>xerces</id> <version>2.2.1</version> <properties> <gump.project>xml-xerces</gump.project> </properties> </dependency> Maybe we should set these dependencies also in xdoclet-plugins and generama. After all GRA-2 patch source is for Xerces2. http://www.burnthacker.com/archives/000086.html Until we do this, or a workaround, I expect linux users to continue with troubles :( PS: Greg, btw, Are you working in windows??
smime.p7s
Description: S/MIME cryptographic signature
