Skip to content
New issue

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

Deploy the bundle via the dedicated DAV url #1726

Closed
kwin opened this issue Jan 28, 2019 · 0 comments · Fixed by #1727
Closed

Deploy the bundle via the dedicated DAV url #1726

kwin opened this issue Jan 28, 2019 · 0 comments · Fixed by #1727

Comments

@kwin
Copy link
Contributor

kwin commented Jan 28, 2019

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:

<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).

kwin added a commit to kwin/acs-aem-commons that referenced this issue Jan 28, 2019
Fixes "Failed getting intermediate path at http://localhost:4502/apps/.
Reason: Forbidden"

This closes Adobe-Consulting-Services#1726
@justinedelson justinedelson added this to the 4.0.0 milestone Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants