This page contains instructions on how to build and run the Test Project and what issues we see. The launch will eventually fail as the aem-groovy-console will not run on Sling but that is not the goal.
The project contains multiple branches to showcase the various issues where some of the issues are manually fixed to move ahead.
- Branch: issue/package-group
- Ticket: SLING-8626
- Temporary Fix: maven the package group the same name as the Maven group
- Issues:
- The converter's convert() method is not returning feedback on where it placed the files and so it is very difficult to automate it
- Because the CP Converter uses the package group and that one is different from the Maven group the Sling FM Plugin will look up the converted dependency in the package group path but the POM of that file is in the Maven group path which causes conflicts in the Sling FM Plugin.
Branch: issue/manifest Ticket: ??? Temporary Fix: Issue:
All plugin and dependencies of not released code is incorporated into a project local project as well as the Sling Starter Provisioning Model so no further preparations are necessary.
This project is built with standard Maven command:
mvn clean install
To launch it just add the launch profile:
mvn clean install -P launch
Sling will start but you will see many dependency issues but as long as Sling starts we are good here.