Some of our developers periodically check in code and write CVS commit
messages containing invalid characters. For example, people will put in
Ctrl-V+C accidentally, which causes our continuous build to fail with:

BUILD FAILED
File...... /home/jdunn/.maven/cache/maven-xdoc-plugin-1.8/plugin.jelly
Element... x:parse
Line...... 120
Column.... 48
Error on line 12 of document
file:/home/jdunn/devel/util/target/changelog.xml :An invalid XML
character (Unicode: 0x16) was found in the CDATA section.
Nestedexception: An invalid XML character (Unicode: 0x16) was found in
the CDATA section.
Total time: 19 seconds
Finished at: Fri Jan 28 16:55:21 EST 2005

Short of filtering this stuff out on check-in, is there any way to make
Maven ignore invalid characters in the SCM history?

- Julian

-- 
-- Julian C. Dunn, B.A.Sc, P.Eng.  <[EMAIL PROTECTED]>
-- Platform Administrator, CBC.ca Production & Operations
-- Office: 2C310-Q  *  Tel.: (416) 205-3311 x5592


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to