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
simila
On Friday 31 March 2017 14:39:46 Andreas Schaefer Sr. wrote:
> For something else I delved into Sling Provisioning and I
> came up with a way to import Thymeleaf. Not sure if that
> is the best way but it seems to work.
>
> When I add a file called thymeleaf.txt to
> launchpad/builder/src/main/pr
Hey Andreas,
You can make your own custom launchpads with a maven project.
In your pom.xml you use the following plugin:
org.apache.sling
slingstart-maven-plugin
true
Until sling 9 is released you use the following snapsh
>
> 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
>
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 ha