The JLS makes this clear:
It is permitted, but discouraged as a matter of style, to redundantly specify the
public
and/orabstract
modifier for a method declared in an interface.
More Related Contents:
- Type List vs type ArrayList in Java [duplicate]
- Java Pass Method as Parameter
- How do you find all subclasses of a given class in Java?
- Custom fonts and XML layouts (Android)
- Find Java classes implementing an interface [duplicate]
- Why would a static nested interface be used in Java?
- Polymorphism: Why use “List list = new ArrayList” instead of “ArrayList list = new ArrayList”? [duplicate]
- Abstract class vs Interface in Java
- Protected in Interfaces
- Should we @Override an interface’s method implementation?
- Java – declaring from Interface type instead of Class
- When should I use an interface in java? [closed]
- List versus ArrayList as reference type?
- Stand-alone Java code formatter/beautifier/pretty printer? [closed]
- Why an abstract class implementing an interface can miss the declaration/implementation of one of the interface’s methods?
- Why are class static methods inherited but not interface static methods?
- Do/can abstract classes replace interfaces? [duplicate]
- NotSerializableException on anonymous class
- Modifier Keyword order in Java
- Java generics – Make Generic to extends 2 interfaces
- Should you always Code To Interfaces In Java [closed]
- For a boolean field, what is the naming convention for its getter/setter?
- Why would both a parent and child class implement the same interface?
- Can an interface method have a body?
- Are defaults in JDK 8 a form of multiple inheritance in Java?
- interface as a method parameter in Java
- static initialization in interface
- Java Interface Usage Guidelines — Are getters and setters in an interface bad?
- Attributes / member variables in interfaces?
- How to reference a generic return type with multiple bounds