[
https://issues.apache.org/jira/browse/SLING-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956844#comment-15956844
]
Konrad Windszus commented on SLING-6662:
----------------------------------------
bq. We don't have a strict naming pattern and I guess having SPI in API has
historical reasons (we didn't cleary distinguish between API and SPI in the
past).
SPI is API as well (https://en.wikipedia.org/wiki/Service_provider_interface),
therefore I still think naming the according bundle API makes sense!
bq. Naming packages or modules impl is unfavorable when you also provide base
classes for extension or support classes which are not part of API or SPI
(internal for packages containing private implementation classes is IMHO a
better choice) and alternative implementations in other modules (see discovery
or event).
I agree but don' t see how this is violated by the current state of
validation.core nor validation.api
> Move DefaultValidationFailure and DefaultValidationResult out of package
> org.apache.sling.validation.spi
> --------------------------------------------------------------------------------------------------------
>
> Key: SLING-6662
> URL: https://issues.apache.org/jira/browse/SLING-6662
> Project: Sling
> Issue Type: Improvement
> Components: Extensions, Validation
> Reporter: Oliver Lietz
> Assignee: Konrad Windszus
> Fix For: Validation 1.0.0
>
>
> Move DefaultValidationFailure and DefaultValidationResult to Validation Core
> (package {{org.apache.sling.validation.support|base}}) to keep Validation API
> lean.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
