[
https://issues.apache.org/jira/browse/SLING-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614684#comment-16614684
]
David Bosschaert commented on SLING-7925:
-----------------------------------------
Hi [~simone.tripodi], thanks a lot for your patches!
Another option could be to add the api-region validation to the feature model
analyser (https://github.com/apache/sling-org-apache-sling-feature-analyser)
which already contains some other checks on the feature model files, and then
have the analyser run as part of the validation from the maven plugin. That way
the api regions would still be automatically checked, but also other analyser
tasks will also run. WDYT?
> Donating a new Mojo which is able to validate APIs/Regions
> -----------------------------------------------------------
>
> Key: SLING-7925
> URL: https://issues.apache.org/jira/browse/SLING-7925
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model, Maven Plugins and Archetypes
> Reporter: Simone Tripodi
> Assignee: David Bosschaert
> Priority: Major
> Attachments: SLING-7925.1.patch, SLING-7925.patch
>
>
> According to open discussion on SLING-7779, I started using a subset of the
> features described, then in order to produce valid results I had the need to
> implement a validator which detects discrepancies between what is declared in
> the {{export}} section of each region and what is really exported by bundles
> enlisted in the feature itself.
> The verification works in order to accept a feature files directory as a
> input, supports the typical {{(in|ex)cludes}} Maven pattern, validation works
> locally per-featurefile and doesn't support the global validation.
> Patch, including integration tests, is coming!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
