[jira] [Commented] (SLING-3540) JCR Install bundle plugin can not be installed on an out-of-the-box launchpad

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987701#comment-13987701 ] 

Bertrand Delacretaz commented on SLING-3540:
--------------------------------------------

The best would be for maven-sling-plugin to create the required folder structure before PUTting the bundle (with appropriate logging to avoid surprises).

I vaguely remember a discussion about adding that feature, forgot what the outcome was.

> JCR Install bundle plugin can not be installed on an out-of-the-box launchpad
> -----------------------------------------------------------------------------
>
>                 Key: SLING-3540
>                 URL: https://issues.apache.org/jira/browse/SLING-3540
>             Project: Sling
>          Issue Type: Bug
>          Components: Maven Plugins and Archetypes
>    Affects Versions: JCRInstall Bundle Archetype 1.0.0
>            Reporter: Robert Munteanu
>
> {code}[INFO] Installing Bundle com.example.jcrbundle(/home/rmuntean/tmp/jcrbundle/target/jcrbundle-1.0-SNAPSHOT.jar) to http://localhost:8080/libs/sling/install via PUT
> [ERROR] Installation failed, cause: Conflict{code}
> The reason is that the default Sling launchpad does not have a /libs/sling/install directory structure out of the box. The workaround is to create it, e.g. with curl
> {code}
> curl -u admin:admin -X MKCOL http://localhost:8080/libs
> curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling
> curl -u admin:admin -X MKCOL http://localhost:8080/libs/sling/install
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)