[jira] [Updated] (SLING-10779) ContentPackage2FeatureModelConverter.getAclManager should never return null
[ https://issues.apache.org/jira/browse/SLING-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-10779: Fix Version/s: Content-Package to Feature Model Converter 1.1.16 (was: Content-Package to Feature Model Converter 1.1.14) > ContentPackage2FeatureModelConverter.getAclManager should never return null > --- > > Key: SLING-10779 > URL: https://issues.apache.org/jira/browse/SLING-10779 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Angela Schreiber >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.16 > > > {{ContentPackage2FeatureModelConverter.getAclManager}} is used across the > converter code base and always expected to be not-null. so, instead of > defining it as 'nullable' we should find ways to make sure it is always > present on the converter. this would allow to get rid of > Objects.requireNotNull and the warnings about potential NPE where the check > is missing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10779) ContentPackage2FeatureModelConverter.getAclManager should never return null
[ https://issues.apache.org/jira/browse/SLING-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10779: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > ContentPackage2FeatureModelConverter.getAclManager should never return null > --- > > Key: SLING-10779 > URL: https://issues.apache.org/jira/browse/SLING-10779 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Angela Schreiber >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > {{ContentPackage2FeatureModelConverter.getAclManager}} is used across the > converter code base and always expected to be not-null. so, instead of > defining it as 'nullable' we should find ways to make sure it is always > present on the converter. this would allow to get rid of > Objects.requireNotNull and the warnings about potential NPE where the check > is missing. -- This message was sent by Atlassian Jira (v8.20.1#820001)