You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2020/05/25 14:09:00 UTC
[jira] [Updated] (SLING-9462) Sub Maven Project fails in Check
Preprocessor Run
[ https://issues.apache.org/jira/browse/SLING-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
A. J. David Bosschaert updated SLING-9462:
------------------------------------------
Fix Version/s: (was: slingfeature-maven-plugin 1.3.4)
slingfeature-maven-plugin 1.3.6
> Sub Maven Project fails in Check Preprocessor Run
> -------------------------------------------------
>
> Key: SLING-9462
> URL: https://issues.apache.org/jira/browse/SLING-9462
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: slingfeature-maven-plugin 1.3.2
> Reporter: Andreas Schaefer
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.3.6
>
>
> When I have a parent POM (package 'pom') and only have sub modules in there and then a submodule wants to create a Feature Model using 'include-artifact' then the build fails with the message: 'The slingfeature preprocessor did not run'.
> Running the build from the child does just fine.
>
> Debugging this yields a strange issue where the ProjectHelper.storeProjectInfo() is using another Maven Project instance (info.project) than the one given to the ProjectHelper.checkProcessorRun() - hence the failure.
>
> This is very irritating because the suggested fix is not fixing it (extensions = true).
>
> My guess is that this is a problem with sub modules where the testing is not done with the same Maven Project instance and hence the stored Context Value is then not found.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)