kwin edited a comment on pull request #32: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/32#issuecomment-943109897
If you need to validate content packages from a custom feature model analyser either 1. call the maven plugin in a forked Java process to validate (in case you can make sure that Maven is always available) or 1. use the Validator API in that analyser. But please don't just do simple validation without the FileVault Validation module! But still: Even a third party without having access to either pom.xml or sources can just validate content packages with the aforementioned tools (outside the feature model analyser). Why do you need to include it in the feature analyser? Instead of trying to do everything with one tool I just propose to use two tools! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
