On Sat, 2019-10-05 at 23:32 -0500, Daniel Klco wrote:
(snip)
> I've put together a simple project archetype for Sling CMS here, but
> I'd
> wonder if it'd be similar to back it into the overall
> sling-project-archetype as a separate content option from the sample
> content. Options for sample
Sorry to add a wrinkle here, but I'm also wondering if it'd make sense to
make the sample options more flexible than just merge, keep or delete to
support different content use cases. For the Sling CMS reference, it'd be
nice to be able to populate more content than you'd need for a "base" Sling
On Thu, 2019-09-12 at 09:28 -0700, Andreas Schaefer wrote:
> The only problem is the number of parameters that have to be handled
> as all parameters must be specified when the archetype is launched.
+1, that is a big problem and we should keep it under control.
Robert
kage projects below a /content-packages folder
> > it's not unusual you create more of them for bigger projects, and
> > then they are nicely grouped.
> >
> > stefan
> >
> > > -Original Message-
> > > From: Konrad Windszus [mailto:konra...@gmx
not unusual you create more of them for bigger projects, and then they are
nicely grouped.
stefan
-Original Message-
From: Konrad Windszus [mailto:konra...@gmx.de]
Sent: Thursday, September 12, 2019 5:53 PM
To: dev@sling.apache.org
Subject: Re: [hackathon] maven archetypes
Definitely +1
folder
it's not unusual you create more of them for bigger projects, and then they are
nicely grouped.
stefan
>-Original Message-
>From: Konrad Windszus [mailto:konra...@gmx.de]
>Sent: Thursday, September 12, 2019 5:53 PM
>To: dev@sling.apache.org
>Subject: Re: [hackathon] m
With respect to C:
The Sling Project Archetype has two versions of each module in it:
- plain (no code)
- sample code
The archetype can do the following:
- merge samples into module aka having only one module
- delete samples
- keep them separate. Only the plain code module is active in the
Definitely +1 on having only one archetype. In case D is too much effort, we
could even leave it out.
A maintained archetype is better than what we currently have.
And it should be pretty easy for every developer to just copy over from a
blueprint project created from the archetype only the
On Thu, 2019-09-05 at 14:43 +, Stefan Seifert wrote:
> - currently there are lots of sling maven archetypes, and most of
> them not well maintained
> - we would favor to have only one single "project" archetypes,
> probably the new "project" archetype contributed by andy
> - add parameters to
- currently there are lots of sling maven archetypes, and most of them not well
maintained
- we would favor to have only one single "project" archetypes, probably the new
"project" archetype contributed by andy
- add parameters to switch features on and off, e.g. for generating only with
bundle
10 matches
Mail list logo
