We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For reasons like outlined in adobe/aem-project-archetype#56 and https://issues.apache.org/jira/browse/SLING-7916 the following plugin configuration should be used for the sling-maven-plugin:
sling-maven-plugin
<plugin> <groupId>org.apache.sling</groupId> <artifactId>maven-sling-plugin</artifactId> <configuration <slingUrl>http://${crx.host}:${crx.port}${crx.contextRoot}/crx/repository/crx.default</slingUrl> <slingUrlSuffix>/apps/acs-commons/install</slingUrlSuffix> <deploymentMethod>WebDAV</deploymentMethod> </configuration> </plugin>
That way this works in almost all existing AEM installation (no matter how they are configured).
The text was updated successfully, but these errors were encountered:
Use dedicated path for WebDAV deployment.
70d08e6
Fixes "Failed getting intermediate path at http://localhost:4502/apps/. Reason: Forbidden" This closes Adobe-Consulting-Services#1726
Successfully merging a pull request may close this issue.
For reasons like outlined in adobe/aem-project-archetype#56 and https://issues.apache.org/jira/browse/SLING-7916 the following plugin configuration should be used for the
sling-maven-plugin
:That way this works in almost all existing AEM installation (no matter how they are configured).
The text was updated successfully, but these errors were encountered: