[
https://issues.apache.org/jira/browse/SLING-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614768#comment-16614768
]
Carsten Ziegeler commented on SLING-7925:
-----------------------------------------
[~simone.tripodi] It's a little bit different and I guess the names we choose
are a little bit confusing.
The feature analyser module has two main services: the scanner and the
analyzer. The scanner "scans" features and the individual artifacts like
bundles and extracts information and ultimately creates a FeatureDescriptor for
a whole feature.
The analyzer uses that FeatureDescriptor and passes it to a set of AnalyzerTask
objects - and these analyzer tasks do the analysis. They have access to the
whole feature but also to information about the individual artifacts.
So for this case you could implement an AnalyzerTask
> 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)
