<p>My company is using CVS as our de-facto standard for source control. However, I've heard a lot of people say that SVN is better.</p>

<p>I know SVN is newer, but other than that, I'm unfamiliar with its benefits.</p>

<p>What I'm looking for is a good, succinct comparison of the two systems, noting any advantages or disadvantages of each in a Java/Eclipse development environment.</p>

One of the many comparisons:
http://wiki.scummvm.org/index.php/CVS_vs_SVN
Now this is very specific to that project, but a lot of stuff apllies in general.
Pro Subversion:
Support for versioned renames/moves (impossible with CVS): Fingolfin, Ender
Supports directories natively: It's possible to remove them, and they are versioned: Fingolfin, Ender
File properties are versioned; no more "executable bit" hell: Fingolfin
Overall revision number makes build versioning and regression testing much easier: Ender, Fingolfin
Atomic commits: Fingolfin
Intuitive (directory-based) branching and tagging: Fingolfin
Easier hook scripts (pre/post commit, etc): SumthinWicked (I use it for Doxygen after commits)
Prevents accidental committing of conflicted files: Salty-horse, Fingolfin
Support for custom 'diff' command: Fingolfin
Offline diffs, and they're instant: sev