[SLING-6609] Fix JSR305 annotations for ValueMap.get

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: API 2.16.2
• Fix Version/s: API 2.16.4
• Component/s: API
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 05/Mar/17 11:11
• Updated: 02/Nov/17 15:27
• Resolved: 02/Nov/17 15:27

Description

Currently <T> T get(@Nonnull String name, T defaultValue); does neither define a JSR 305 annotation for the return value nor for the 2nd parameter. It makes sense to define them both as @Nonnull, because if you intend to get null as return value you are supposed to take the other get method (@CheckForNull <T> T get(@Nonnull String name, @Nonnull Class<T> type))

Issue Links

• relates to: SLING-4377 Add JSR305 nullness annotations to Sling API