[
https://issues.apache.org/jira/browse/SLING-11734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-11734.
--------------------------------------
Resolution: Fixed
> ContentPackageScanner does not extract the right artifactId in case of
> multiple pom.properties
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-11734
> URL: https://issues.apache.org/jira/browse/SLING-11734
> Project: Sling
> Issue Type: Bug
> Components: Feature Model Analyser
> Affects Versions: Feature Model Analyser 1.6.8
> Reporter: Niek Raaijmakers
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model Analyser 2.0.0
>
>
> Currently, the ContentPackageScanner gets the first directory available under
> the maven meta-inf folder.
> This works most of the time, as there is usually only 1 properties file
> inside a package.
>
> However in some edge cases, there are multiple. And if the order is that in a
> way that a different package comes first, such as com.google.guava , it will
> take that one instead.
> Example we are extracting com.acs.aem.acs-aem-commons-content-5.4.3.zip >
> acs-aem-commons-bundle-5.3.4.jar
> The META-INF/maven folder contains:
> com.google.guava/failureaccess/pom.properties
> com.adobe.acs/acs-aem-commons-bundle/pom.properties
>
> Now, the first is picked, com.google.guava/failureaccess/pom.properties
>
> What we want is to build in a mechanism that if there are multiple maven
> properties, the contentpackagescanner will check if one of them has a groupId
> (first folder) that matches.
>
> Since the groupId com.adobe.acs is a match, we can use that to pick the right
> properties file.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
