[ 
https://issues.apache.org/jira/browse/SLING-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614702#comment-16614702
 ] 

Simone Tripodi commented on SLING-7925:
---------------------------------------

Hi there [~bosschaert],
my pleasure, I am always glad to cooperate :)

IIUC, the `Analyzer` interface is hit for each detected bundle in each feature, 
right? That wouldn't be helpful unfortunately, it is a too fine-grained 
operation, I am having trouble on sending back the result when all bundles of 
each Feature are analysed.

In the Analyzer we can implement the other way round: checking if all exported 
packages in every bundle are exported in all declared regions, but it doesn't 
make a lot of sense...

[~cziegeler] can you confirm, please?
Many thanks in advance!

> 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)

Reply via email to