cschneider commented on pull request #32: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/32#issuecomment-941973180
@kwin The current version of filevault-package-maven-plugin fully supports this. Unfortunately we have no influence on if / when our customers upgrade to this version. So this validator is meant as a second level check in case the customers do not upgrade. In the docs I plan to recommend to upgrade the filevault-package-maven-plugin to catch this error earlier. Regarding the standalone goal. How would that work practically? I guess we would have to parse the customer git repo for places where they create content packages. Then we would have to run the plugin in these subdirectories. That is quite a big effort and it still would not protect us from the cases where customers add precreated content packages from external sources. -- 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: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
