Parse errors

Hi!

I'm currently working on a project using IntelliJ Idea. I've been generating Javadocs for quite some time but recently there has been some errors that are making me go crazy.

All classes get some kind of parse errors cause the generated files look really strange.

There are asterixs placed in the middle of the text and @param and @return isn't parsed properly. It only works for the last class I added to the project allthough I can't tell any difference between the styles of the comments. There should be the same kind of whitespace too. The problem isn't confined to method comments but also appear in class comments. I've been using the reformatting tool that comes with IntelliJ so everything should be in a unified fashion. The tool shouldn't be the cause of my problems since it has worked fine before.

I save the files to a CVS repository on a Unix machine in case this may cause trouble with the char table somehow. It's not much use to post samples here since the forum won't keep the formatting and whitespace properly.

Are there any general Javadoc allergies that I should know about?

[1148 byte] By [BennyAkessona] at [2007-9-28 14:15:39]
# 1

I noticed another thread regarding this where someone on the Javadoc team said it may be problems with the endline character. It's interesting since the only file that works properly is the last one added. IntelliJ is set to use system dependent endlines when a new file is added. Maybe that file has Windows endline characters (I'm devoloping in Windows) and the other one has been given something else when the files have been commited with CVS. It's strange though since I have deleted all the files in my workspace and checked out another set. That should imply that the same problem would appear on that file too.

BennyAkessona at 2007-7-12 10:40:09 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...
# 2
Now I know what's wrong. I downloaded a hex editor to take a look at those endline characters. The files that do not work have 0x0D as end line chars while the working one has 0x0A. I don't know why they are differing though.
BennyAkessona at 2007-7-12 10:40:09 > top of Java-index,Developer Tools,Debugging and Profiling Tool APIs...