I tried that but for now this does not work with Sling / Composum (call to '/bin/cpm/package.service.html/system/console/bundles/.json’).
After disabling the bundle status with ‘bundleStatusURL’ set to ‘-‘ it fails to handle the response of the installation as Composum returns nothing. Did anyone successfully deployed a package with this on Sling? And if, how? Thanks - Andy Schaefer > On Apr 4, 2017, at 8:44 AM, Roy Teeuwen <r...@teeuwen.be> wrote: > > Hey Andy, > > As you can see in the ticket, there is already something that exists: > >> a good starting point for this may be the wcm.io content package maven >> plugin: >> • >> http://wcm.io/tooling/maven/plugins/wcmio-content-package-maven-plugin/ >> • >> https://github.com/wcm-io/wcm-io-tooling/tree/develop/maven/plugins/wcmio-content-package-maven-plugin > > > Greets, > Roy >> On 4 Apr 2017, at 17:28, Andreas Schaefer Sr. <schaef...@me.com> wrote: >> >> Yes, I was thinking that might be the issue. >> >> Do you guess have already something on Git? >> >> Thanks - Andy Schaefer >> >>> On Apr 4, 2017, at 12:13 AM, Robert Munteanu <romb...@apache.org> wrote: >>> >>> On Tue, 2017-04-04 at 08:32 +0200, Roy Teeuwen wrote: >>>> Hey Andy, >>>> >>>> The license inside might not be good enough ;) >>>> >>>> Greets, >>>> Roy >>>>> On 3 Apr 2017, at 22:50, Andreas Schaefer <schaef...@mac.com> >>>>> wrote: >>>>> >>>>> Why is that necessary? The one from Adobe isn't good enough? >>> >>> IANAL and speaking only as an Apache committer, not as an Adobe >>> employee. >>> >>> That being said, that artifact is not present on Maven central, and on >>> repo.adobe.com the following disclaimer is used >>> >>> This maven2 repository provides access to public artifacts used in >>> conjunction with developing java-based applications on Adobe >>> frameworks. Adobe Terms apply. >>> >>> Adobe terms links to http://www.adobe.com/misc/terms.html . >>> >>> I for one would not use that plugin in Apache Sling applications >>> without legal advice, but a brief look tells me that these are not >>> intended for use with non-Adobe apps. >>> >>> Robert >>> >>>>> >>>>> - Andy Schaefer >>>>> >>>>>> On Apr 3, 2017, at 3:23 AM, Robert Munteanu <romb...@apache.org> >>>>>> wrote: >>>>>> >>>>>> Hi Greg, >>>>>> >>>>>>> On Sat, 2017-04-01 at 13:18 +0200, Greg Fullard wrote: >>>>>>> Hi All >>>>>>> >>>>>>> I see that there is some difference between how content >>>>>>> projects are >>>>>>> handled between the Sling IDE tools and the Maven archetypes. >>>>>>> >>>>>>> >>>>>>> 1. The "Sling Content Project" wizard creates a project with >>>>>>> a >>>>>>> jcr_root >>>>>>> folder which then contains folders and content.xml files. >>>>>>> This is >>>>>>> very >>>>>>> similar to what I'm used to with AEM Archetype 10. >>>>>> >>>>>> In addition to what others have said, there is plan ( with no >>>>>> time >>>>>> commitment ) to add our own content-package Maven plugin, which >>>>>> would >>>>>> make this kind of project usable with Maven. >>>>>> >>>>>> https://issues.apache.org/jira/browse/SLING-6081 >>>>>> >>>>>> Robert >>>>>> >>>>>>> 2. The sling-initial-content-archetype, on the other hand, >>>>>>> generates a >>>>>>> SLING-INF folder with an XML node descriptor file (as >>>>>>> explained at >>>>>>> http://sling.apache.org/documentation/bundles/content-loading >>>>>>> -jcr- >>>>>>> contentloader.html >>>>>>> ) >>>>>>> 3. The Slingbucks example uses JSON descriptor files. >>>>>>> >>>>>>> >>>>>>> Obviously all these methods work, but I'm interested to get an >>>>>>> idea >>>>>>> of what >>>>>>> the recommended method is. Perhaps based on specific criteria >>>>>>> of my >>>>>>> project? >>>>>>> >>>>>>> Much appreciated >>>>>>> >>>>>>> Greg >>>>>>> >>>> >>>> >>> >> >