Why is that necessary? The one from Adobe isn't good enough?

- 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
>> 
> 

Reply via email to