making a class abstract vs making the constructor private

Question

I got a design question in my mind. Suppose if I have a class which has only static methods, what would be the best design option from the following two.

• Make the class abstract
• Make the constructor private, so that no code outside the class can make an object of this class.

Does the choice depend on the situation or there is one best way to go? And why?

Answer 1

Making a class abstract assumes that you want this class to be inherited from. If you want this to happen, then make it abstract.

If you only have static Methods (so it's some kind of utility class) then go with the second way.
Though there is nothing wrong in creating an Instance of this class, as there is no benefit or disadvantage that way, the best practice is to make the constructor private for utility classes.

Answer 2

Let's look at what the developers of standard classes did :

public class Arrays {
    // Suppresses default constructor, ensuring non-instantiability.
    private Arrays() {
    }

public class Collections {
    // Suppresses default constructor, ensuring non-instantiability.
    private Collections() {
    }

I see a pattern here.

This makes sense, since an abstract class implies that the class should be sub-classed, which is not the case when your class is a utility class having only static methods.