I am also not sure why it matters - we switched 3,000,000+ lines of code from subversion to git, but the effort was not really correlated with LOC. The major overhead of switching from subversion to git is the learning hit on the developers (though it is certainly worth it for many of the reasons described in the OP).
I'm not convinced language snobbery is something to be encouraged personally :/ If it was lisp it'd be 200,000 lines of parenthesis, if it were python it'd be 200,000 of significant whitespace, perl? 200,000 of random punctuation characters etc etc.
It's not the language, it's what you do with it that counts.
If someone is writing countless getters and setters, in any language, they're clearly doing something terribly wrong.
Sure, but at the same time all languages were not created equal. Some are better designed and more powerful than others. They're not all just equally great at different things and let's sing "Kum ba yah" together now.
Using your IDE to type code for you is the problem. Not Java. Place the blame where it should be. If a programmer is foolish enough to use an IDE to generate code, and doesn't mind if it's near identical rubbish, then it's not the languages fault anymore.
So could you explain the "right way". I'm not a Java programmer, and googling did not reveal any way to generate accessors other than inserting code in your source file.
An explanation of how you do it would be very valuable, at least to me.
In a comparably sized codebase at my job, there's connectors to this and that idiosyncratic/complex external system (some of which require for example extinct dialects of SOAP), there's legacy cruft, there's systems that draw together multiple providers and present a unified interface, or that distribute commands to the proper subsystem, and there's a ton of reports and front ends and back ends for multiple years of customers, which get remixed and reused.
In Search of Concise Software
Git Breezily Handles our 500,000-line Enterprise Java Project