I'm reading Steven's concern as that the Sling plugin is not assuming the use of the Sling post handler. Which is preventing the use of the POST command to the desired location.
Which is kind of odd. -----Original Message----- From: Stefan Seifert [mailto:sseif...@pro-vision.de] Sent: Wednesday, October 28, 2015 11:16 AM To: users@sling.apache.org Subject: RE: sling-maven-plugin install goal issues hello steven. i use a configuration just like this: <configuration> <slingUrl>${server}/system/console</slingUrl> <user>${sling.user}</user> <password>${sling.pass}</user> <mountByFS>false</mountByFS> </configuration> which posts the bundle to the felix webconsole, deploys and starts them. they are not stored in the repository, though. stefan >-----Original Message----- >From: Steven Walters [mailto:steven.walt...@icidigital.com] >Sent: Wednesday, October 28, 2015 4:11 PM >To: users@sling.apache.org >Subject: sling-maven-plugin install goal issues > >I'm trying to use the sling-maven-plugin install as described at [0]. >I'm now encountering a scenario where I can not use the goal to install >a bundle in a particularly desired way. > >Previously, this was being used successfully within the environment to >place the bundles under the /apps/install folder within the JCR. >So this was configured in the pom.xml such as <configuration> > <slingUrl>${server}/apps/install</slingUrl> > <usePut>true</usePut> > <user>${sling.user}</user> > <password>${sling.pass}</user> ></configuration> >The target system here was a 5.x version of CQ/AEM.
