Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

Maven install on Publish Instance - AEM 6.1

Avatar

Level 10

when I try installing a package or a bundle from maven to publish instance, I am seeing a below error

[ERROR] Failed to execute goal org.apache.sling:maven-sling-plugin:2.1.0:install
 (default) on project testsite.core: Installation on http://localhost:4503/crx/r
epository/crx.default/apps/testsite/install/ failed, cause: Installation failed,
 cause: Method Not Allowed -> [Help 1]

where as it works fine if I install it on author instance. 

Note: I have the project and the install folder under /apps

I was able to build the same in AEM 5.6.1. Am I missing anything here ??

1 Accepted Solution

Avatar

Correct answer by
Level 10

@Jitendra and @Kautuk,

I had already created 'install' folder and it exists in /apps folder as I mentioned in my post.

@kautuk

making <usePut>false</usePut> will use POST and it would again fail for publish instance. 

Instead, I was able to fix this issue by removing the <usePut> tag itself.

View solution in original post

6 Replies

Avatar

Level 9

You can try creating "/apps/testsite/install" manually and then deploy code again.

Jitendra

Avatar

Administrator

Hi Lokesh

Please have a look at this community article:-

Case 1:-

    Link:- https://mkbansal.wordpress.com/2013/02/22/abobe-cq5-deployment-error-of-code-mojoexecutionexception/

    Link:- http://stackoverflow.com/questions/23183751/unable-to-deploy-the-osgi-bundle-using-auto-deploy-profi...

    Root cause: This error occurred because build script is trying to deploying the packet under /apps/testsite/install directory which actually do not exists.

    Solution:Create folder named "testsite" & "testsite/install" under "apps". Use CRXDE Light to create folders.

Case 2:- 

    Link:- https://github.com/Adobe-Marketing-Cloud/aem-project-archetype/issues/56

    // Change the maven-sling-plugin configuration to <usePut>false</usePut>, then the bundle install works as expected.

I hope this would help you.

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

Avatar

Correct answer by
Level 10

@Jitendra and @Kautuk,

I had already created 'install' folder and it exists in /apps folder as I mentioned in my post.

@kautuk

making <usePut>false</usePut> will use POST and it would again fail for publish instance. 

Instead, I was able to fix this issue by removing the <usePut> tag itself.

Avatar

Administrator

bsloki wrote...

@Jitendra and @Kautuk,

I had already created 'install' folder and it exists in /apps folder as I mentioned in my post.

@kautuk

making <usePut>false</usePut> will use POST and it would again fail for publish instance. 

Instead, I was able to fix this issue by removing the <usePut> tag itself.

 

Yes, default value of this tag is false. so removing this would also help.

Link:- http://sling.apache.org/site/sling.html#Sling-install

       
usePutfalsesling.usePutIf a simple HTTP PUT should be used instead of the standard POST to the felix console. In the uninstall goal, a HTTP DELETE will be used.

 

Thanks and Regards

Kautuk Sahni



Kautuk Sahni