I haven't used a current version of IBM's WSAD/RAD (whatever they call it today) or IntelliJ IDEA for about 10 years. Since retiring to no more than temp, part-time freelance, I use nothing but Eclipse Classic (Java JEE version) with plugins for a few special, extra things related to UIE, PHP, and version control. However, back in my corporate days (when dinosaurs walked the Earth) the defaults for both WSAD and IntelliJ were to provide TODO auto-stubs for both getters and setters any time you declared a variable in class scope. I note those platform defaults by way of observing that the JEE aspects embedded in the assumptions of the IDEs' creators may have unduly influence developers to think of public mutators and accessors as non-optional.
I think Mark got it right. If a field/variable can, well, vary under manipulation by its parent or close relatives, but should be protected from direct manipulation by strangers, then you offer a getter. MAYBE you provide a non-operational setter to make clear to other developers that there should be no mutation allowed by external calls (I think lack of setter documents that just as well, but I don't write the coding bible for every shop).
There are cases in which public setters are entirely reasonable and correct. Make sure yours is one of those cases before creating that setter.
Bottom line, I can go either way with no strong (pun intended - <strong>strong</strong>) leaning, but I want there to be a shop-wide bible about these sorts of "standards" and lightning strikes upon heretics. At least locally, let's all be on the same page.