Description of problem: Getting a message. " [Fatal Error] :1:1: Content is not allowed in prolog. " on the console along with some things in the log when trying to build some projects from eclipse.org Version-Release number of selected component (if applicable): eclipse-jdt-3.0.0-22 How reproducible: always Steps to Reproduce: 1. Add cvs repository :pserver:anonymous.org:/home/eclipse. 2. Checkout the following plugins: org.apache.ant, org.apache.xerces, org.eclipse.ant.core, org.eclipse.core.boot, org.eclipse.core.runtime. Actual results: When it does the automatic build you end up with " [Fatal Error] :1:1: Content is not allowed in prolog. " on the console and a log consisting of " !SESSION Aug 04, 2004 17:04:32.172 --------------------------------------------- eclipse.buildId=200406251208 java.fullversion=J2RE 1.4.2 IBM build cxppc321420-20040626 (JIT enabled: jitc) BootLoader constants: OS=linux, ARCH=ppc, WS=gtk, NL=en_US !ENTRY org.eclipse.team.cvs.core 2 0 Aug 04, 2004 17:04:32.173 !MESSAGE CVS file /org.eclipse.core.runtime/schema/contentTypes.exsd either contains invalid line endings on the server (CR/LF instead of just LF) or is a binary file that is not marked as -kb. !ENTRY org.eclipse.team.cvs.core 2 0 Aug 04, 2004 17:04:32.224 !MESSAGE CVS file /org.eclipse.core.runtime/schema/products.exsd either contains invalid line endings on the server (CR/LF instead of just LF) or is a binary file that is not marked as -kb. " Expected results: No "Fatal Error" and no log Additional info: Should investigate if this exists in eclipse.org and report there if it does.
Same error occurrs on x86 and ia64 as well. This only seems to happen with the IBM JVM, not BEA. (1.4.2)
Developer Suite is out of support, CVS has been deprecated upstream and build system changed - aka everything. Closing.