We found that the aura of authority given by having a real book helped. I bought Scott Ambler's Elements of Java Style for everybody on the team, and published a very short list of exceptions.
If your team all uses the same
IDE, get as much of your style into the code formatter as possible. I use the formatters in Eclipse and Visual Age often. It's nice to type or refactor at maximum speed without worrying about indentation and alignment.
Finally, if you want to go all the way on this, look into an automated style checker. JTest is one example. I find them way too finicky about unimportant things, but it might be just the thing to bring a team into line.
[ January 01, 2004: Message edited by: Stan James ]