Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade to filevault-package-maven-plugin 1.1.4
See original GitHub issueThe newly added validation capabilities (http://jackrabbit.apache.org/filevault-package-maven-plugin/validators.html) are beneficial for all projects, therefore the archetype should be updated to use the filevault-package-maven-plugin in version 1.1.0 and all content-packages within the archetype should be explicitly marked as a specific package type != mixed (instead of relying on automated tagging).
This is especially helpful for AEM as a Cloud Service (https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/developing/aem-project-content-package-structure.html#package-types)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This issue should be fixed in the upcoming f-p-m-p 1.1.2.
@kwin can you please review the PR? Thanks!