[ https://issues.apache.org/jira/browse/SLING-5335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167226#comment-15167226 ]
Konrad Windszus commented on SLING-5335: ---------------------------------------- Applied with slight modifications in [r1732304|https://svn.apache.org/r1732304]. Now Maven 3 is required since the parameter deploymentMethod is an enum type which is only supported since Maven 3 (https://issues.apache.org/jira/browse/MNG-4292). > maven-sling-plugin: Allow installing bundles through SlingPostServlet > mechanisms > -------------------------------------------------------------------------------- > > Key: SLING-5335 > URL: https://issues.apache.org/jira/browse/SLING-5335 > Project: Sling > Issue Type: New Feature > Components: Maven Plugins and Archetypes > Reporter: Steven Walters > Assignee: Konrad Windszus > Priority: Minor > Fix For: Maven Sling Plugin 2.1.8 > > > Add an additional route of installing bundles in maven-sling-plugin through > the SlingPostServlet mechanisms. > Currently, there are only two methodologies supported for installing (and > uninstall) bundles: > # Through POSTing to the Felix Web Console > # Through PUTing to WebDAV > By adding the ability to install through SlingPostServlet, bundles can be > deployed into the resource tree (JCR) when WebDAV is not installed. > For maintaining full-backwards compatibility, the proposition here is the > addition of another boolean flag to the Mojo named {{useSlingPost}} that > defaults to {{false}}. > Altering this new flag to be the value {{true}} will trigger the use of the > new methodology. -- This message was sent by Atlassian JIRA (v6.3.4#6332)