Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-04 Thread Roy Teeuwen
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/ > • >

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-04 Thread Andreas Schaefer Sr.
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 wrote: > > On Tue, 2017-04-04 at 08:32 +0200, Roy Teeuwen wrote: >> Hey Andy, >> >> The license inside might not

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-04 Thread Robert Munteanu
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 > > wrote: > > > > Why is that necessary? The one from Adobe isn't good enough? IANAL and

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-04 Thread Roy Teeuwen
Hey Andy, The license inside might not be good enough ;) Greets, Roy > On 3 Apr 2017, at 22:50, Andreas Schaefer wrote: > > Why is that necessary? The one from Adobe isn't good enough? > > - Andy Schaefer > >> On Apr 3, 2017, at 3:23 AM, Robert Munteanu

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-03 Thread Andreas Schaefer
Why is that necessary? The one from Adobe isn't good enough? - Andy Schaefer > On Apr 3, 2017, at 3:23 AM, Robert Munteanu 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

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-03 Thread Robert Munteanu
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 >

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-01 Thread Andreas Schaefer Sr.
Hi Greg One difference between an JCR Content Package (ZIP file) is that you can use the exploded tree inside the Eclipse or IntelliJ plugin and edit / deploy / import (from server) one file at a time. With the Bundle Content you have to deploy it as an entire bundle. If working with JSon you

Re: Different ways to define initial content :: Content.xml vs Json equivalent

2017-04-01 Thread Chris Millar
> > 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 >