If you define
tableOfContents=false
in the page properties, then no ToC is rendered now
Carsten
Bertrand Delacretaz wrote
> On Wed, Oct 4, 2017 at 3:58 PM, Carsten Ziegeler wrote:
>> ...is there any way to surpress the creation of a ToC
>> for a page? The releases page
I removed the commit info and removed the link to the git commit. Author
and date are now displayed in the center of the page.
Carsten
Bertrand Delacretaz wrote
> Hi,
>
> On Wed, Oct 4, 2017 at 4:14 PM, Carsten Ziegeler wrote:
>> ...The commit info has imho no purpose
I moved it to the bottom of the page
Carsten
Bertrand Delacretaz wrote
> On Wed, Oct 4, 2017 at 12:37 PM, Robert Munteanu wrote:
>> ...We could add them at the bottom of the page for now. I was sort of used
>> to that from Wikipedia...
>
> Again, feel free to fix as
[
https://issues.apache.org/jira/browse/SLING-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz closed SLING-6928.
---
> Remove servlets.compat and commons.json from launchpad.testing
>
[
https://issues.apache.org/jira/browse/SLING-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-6928:
Component/s: Testing
> Remove servlets.compat and commons.json from launchpad.testing
>
[
https://issues.apache.org/jira/browse/SLING-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-6928:
Fix Version/s: Launchpad Integration Tests 1.0.4
> Remove servlets.compat and commons.json from
[
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191611#comment-16191611
]
Andrei Dulvac edited comment on SLING-6868 at 10/4/17 5:26 PM:
---
[
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191611#comment-16191611
]
Andrei Dulvac commented on SLING-6868:
--
[~cziegeler], after using latest bundledresource and hapi
Sorry, I missed the point that web sites can only be published if the source
files are in Git [1].
If I understand correctly the only thing that the maven-scm-publish-plugin
would do is committing the target site to the asf-branch (what we currently
need to do manually).
So for me 1 & 2 are not
Robert Munteanu created SLING-7179:
--
Summary: Jira integration for commits
Key: SLING-7179
URL: https://issues.apache.org/jira/browse/SLING-7179
Project: Sling
Issue Type: Sub-task
On Wed, Oct 4, 2017 at 3:58 PM, Carsten Ziegeler wrote:
> ...is there any way to surpress the creation of a ToC
> for a page? The releases page looks a little bit stupid atm :)..
Not currently but patches welcome ;-)
-Bertrand
On Wed, Oct 4, 2017 at 12:37 PM, Robert Munteanu wrote:
> ...We could add them at the bottom of the page for now. I was sort of used
> to that from Wikipedia...
Again, feel free to fix as desired.
However I think our site would greatly benefit from a graphical
redesign, and
Hi,
On Wed, Oct 4, 2017 at 4:14 PM, Carsten Ziegeler wrote:
> ...The commit info has imho no purpose for the reader of a page. So let's
> drop it...
Feel free to fix as desired, I have no strong feelings - just took
advantage of the info that the git log provides.
On Wed, Oct 4, 2017 at 12:16 PM, Konrad Windszus wrote:
> ...Once we fixed all bugs in our templates, the diff on the MD source files
> is IMHO enough...
You forgot the tag ;-)
Templates will evolve "forever", we might upgrade JBake, use a
different JDK which exposes
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-4752:
---
Assignee: (was: Carsten Ziegeler)
> New resource query API
>
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-4752:
Fix Version/s: (was: Resource Resolver 1.5.32)
(was: JCR Resource
[
https://issues.apache.org/jira/browse/SLING-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7178:
---
Description: The new sling site publish process is a bit manual. We should
be able to
Robert Munteanu created SLING-7178:
--
Summary: Allow publishing the Sling site using Maven
Key: SLING-7178
URL: https://issues.apache.org/jira/browse/SLING-7178
Project: Sling
Issue Type:
On Wed, 2017-10-04 at 12:16 +0200, Konrad Windszus wrote:
> > On 4. Oct 2017, at 12:11, Bertrand Delacretaz > rg> wrote:
> >
> > On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus
> > wrote:
> > > ...I prefer 2 to not pollute the Sling Site Git repo with
>
I think "headless" puts us into a specific bucket. You can build
anything with Sling, being it headless or not. AEM is definitely not
headless :) I think it doesn't make sense for a framework to use that
characterisation, otherwise a lot of frameworks are headless (in the
sense of not having a UI)
Hi Karl,
On Wed, Oct 4, 2017 at 3:44 PM, Karl Pauls wrote:
> ...3. It is more than 100 words :-)..
I don't think that's important, "short" is good enough IMO.
Ruben suggests "headless" which I like (and it's a good excuse for
many of our examples UIs ;-)
So two
Hi,
do we really need all the details on every page of who changed that
page, when and especially including the commit info?
I definitely see a reason for when. I'm fine with who but already fail
to see the point.
The commit info has imho no purpose for the reader of a page. So let's
drop it
[
https://issues.apache.org/jira/browse/SLING-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz updated SLING-6928:
Summary: Remove servlets.compat and commons.json from launchpad.testing
(was: Remove
That would be great
Carsten
Robert Munteanu wrote
> On Wed, 2017-10-04 at 12:34 +0200, Carsten Ziegeler wrote:
>> That's a great idea, thanks Bertrand
>>
>> But :) can we maybe display the tags at some other place? At the top
>> they move the real content some lines further down. Leaving less
Hi,
The vote has passed with the following result :
+1 (binding): Robert Munteanu, Stefan Seifert, Carsten Ziegeler
I will promote the artifacts to the central Maven repository and update the
site. May I ask a PMC member to copy the artifacts?
Regards,
Tomek
--
Tomek Rękawek | Adobe Research
Hi
as a first step I moved all releases into a separate "releases" page and
removed all of them from the news page. Our news now look a little bit
empty...
On a related matter, is there any way to surpress the creation of a ToC
for a page? The releases page looks a little bit stupid atm :)
On Wed, Oct 4, 2017 at 8:34 AM, Bertrand Delacretaz
wrote:
> Hi,
>
> On Sat, Sep 30, 2017 at 12:09 PM, Carsten Ziegeler
> wrote:
>> ...This would keep our main page fairly short and we just need to improve
>> the introduction "Sling in 100 words"..
[
https://issues.apache.org/jira/browse/SLING-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Lietz resolved SLING-7177.
-
Resolution: Done
[r1811065|https://svn.apache.org/r1811065]
Oliver Lietz created SLING-7177:
---
Summary: Switch to RepositoryInitializer factory configurations
Key: SLING-7177
URL: https://issues.apache.org/jira/browse/SLING-7177
Project: Sling
Issue
On Wed, 2017-10-04 at 12:34 +0200, Carsten Ziegeler wrote:
> That's a great idea, thanks Bertrand
>
> But :) can we maybe display the tags at some other place? At the top
> they move the real content some lines further down. Leaving less room
> for the page content.
We could add them at the
That's a great idea, thanks Bertrand
But :) can we maybe display the tags at some other place? At the top
they move the real content some lines further down. Leaving less room
for the page content.
Carsten
Bertrand Delacretaz wrote
> Hi,
>
> Start at http://sling.apache.org/tags/core.html
Totally agree with what Karl said.
One major aspect of the new feature based model is that it describes
what a feature is and how features are combined and how the result looks
like.
Any tooling can then act on this. This will allow us to create Karaf
features or an OSGi subsystem or launch it
[
https://issues.apache.org/jira/browse/SLING-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191091#comment-16191091
]
Robert Munteanu commented on SLING-7176:
Absolutely, we should still publish the generated README
> On 4. Oct 2017, at 12:11, Bertrand Delacretaz wrote:
>
> On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus wrote:
>> ...I prefer 2 to not pollute the Sling Site Git repo with generated
>> artifacts...
>
> But it's *very* useful to be able to see the
[
https://issues.apache.org/jira/browse/SLING-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191087#comment-16191087
]
Konrad Windszus commented on SLING-7176:
bq. I've been thinking about an idea of scripting README
+1
Stefan Seifert wrote
> +1
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191084#comment-16191084
]
Robert Munteanu commented on SLING-7176:
I've been thinking about an idea of scripting README
[
https://issues.apache.org/jira/browse/SLING-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191082#comment-16191082
]
Konrad Windszus commented on SLING-7176:
bq. For bundles which have website docs we might add a
On Wed, Oct 4, 2017 at 12:07 PM, Konrad Windszus wrote:
> ...I prefer 2 to not pollute the Sling Site Git repo with generated
> artifacts...
But it's *very* useful to be able to see the diffs of the published
content before pushing them live.
-Bertrand
On Wed, Oct 4, 2017 at 12:03 PM, Oliver Lietz wrote:
> ...I prefer having a good
> README or module "site" and only documenting high-level concepts or general
> stuff in Sling's site (and wiki)...
+1
-Bertrand
I prefer 2 to not pollute the Sling Site Git repo with generated artifacts.
But even with 2 we should have an according Jenkins Job which executes this
Maven Build & Deploy automatically.
> On 2. Oct 2017, at 21:33, Robert Munteanu wrote:
>
> Hi,
>
> I think we can
On Tuesday 03 October 2017 15:50:17 Konrad Windszus wrote:
> I think we also once discussed on the mailing list where to put bundle
> documentation: either in the readme or in the site itself. Unfortunately I
> couldn't find the according thread. Please help me with the link if you
> have it
+1
On Wed, Oct 4, 2017 at 12:00 PM, Carsten Ziegeler wrote:
> If we can agree on starter, I guess we should change the artifact id
+1
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191077#comment-16191077
]
Bertrand Delacretaz commented on SLING-7176:
I'd prefer using the name "modules" rather than
If we can agree on starter, I guess we should change the artifact id
from o.a.s.launchpad to o.a.s.starter but leave the version. so
basically the "first" release of starter would be 10
I would then call my little startup bundle starter.startup :)
Regards
Carsten
Carsten Ziegeler wrote
> I
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
Thanks for the pointers. I created
https://issues.apache.org/jira/browse/SLING-7176 to track this.
Feel free to extend it with your own ideas.
> On 4. Oct 2017, at 11:49, Bertrand Delacretaz wrote:
>
> Hi,
>
> On Wed, Oct 4, 2017 at 9:57 AM, Robert Munteanu
On Wed, 2017-10-04 at 11:49 +0200, Bertrand Delacretaz wrote:
> Hi,
>
> On Wed, Oct 4, 2017 at 9:57 AM, Robert Munteanu
> wrote:
> > ...The 'canonical' way of doing this is by accessing https://api.gi
> > thub.co
> > m/orgs/${github_org}/repos and filtering based on the repo
Hi,
We solved 1 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12341646
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1795/
You can use this UNIX script to download the release and verify the signatures:
Hi,
On Wed, Oct 4, 2017 at 9:57 AM, Robert Munteanu wrote:
> ...The 'canonical' way of doing this is by accessing https://api.github.co
> m/orgs/${github_org}/repos and filtering based on the repo name...
Note that this would require handling multiple pages, it looks like
[
https://issues.apache.org/jira/browse/SLING-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16189515#comment-16189515
]
Oliver Lietz edited comment on SLING-7167 at 10/4/17 9:46 AM:
--
All of our
+1
Stefan Seifert wrote
>
>> -Original Message-
>> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>> Sent: Wednesday, October 4, 2017 8:34 AM
>> To: dev
>> Subject: Re: [Site] Improving the main site
>>
>> Here's my draft, feel free to tweak:
>>
>> Apache Sling is a
>-Original Message-
>From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
>Sent: Wednesday, October 4, 2017 8:34 AM
>To: dev
>Subject: Re: [Site] Improving the main site
>
>Here's my draft, feel free to tweak:
>
>Apache Sling is a REST-based Web framework based on a hierarchical
On Wednesday 04 October 2017 00:43:14 Karl Pauls wrote:
> On Tue, Oct 3, 2017 at 4:37 PM, Bertrand Delacretaz
>
> wrote:
> > On Tue, Oct 3, 2017 at 3:58 PM, Konrad Windszus wrote:
> >> ..."Sling Reference Distribution"
> >
> > I like that, and the
[
https://issues.apache.org/jira/browse/SLING-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso resolved SLING-7152.
--
Resolution: Duplicate
> Unclosed ResourceResolver in
>
Hmm good point, I think we can leave out the "standalone", it's either
Sling App or Sling Web App.
As a first timer I would have no idea what "Standalone" means.
But that's just my 2c
Carsten
Oliver Lietz wrote
> On Wednesday 04 October 2017 09:42:44 Carsten Ziegeler wrote:
>> I like
On Wednesday 04 October 2017 09:42:44 Carsten Ziegeler wrote:
> I like Starter as well (and agree that quickstart would be nice but we
> shouldn't use it due to the mentioned problems)
>
> So this would be Sling Starter as the basic name, Sling Starter
> Application for our jar and Sling Starter
On Wed, 2017-10-04 at 10:01 +0200, Carsten Ziegeler wrote:
> Robert Munteanu wrote> On Tue, 2017-10-03 at 11:52 +0200, Carsten
> Ziegeler wrote:
>
> > > > 2. Reading the section on configuration merging, it is not
> > > > clear to
> > > > me
> > > > if merging is merging of values or overriding
On Wed, 2017-10-04 at 10:01 +0200, Konrad Windszus wrote:
> > On 4. Oct 2017, at 09:57, Robert Munteanu
> > wrote:
> >
> > On Tue, 2017-10-03 at 17:03 +0200, Konrad Windszus wrote:
> > > > On 3. Oct 2017, at 16:35, Bertrand Delacretaz > > > he.o
> > > >
+1 for Sling Starter
(Didn't think about the name clash of Sling Distribution, thanks for the hint
Robert)
> On 4. Oct 2017, at 09:51, Karl Pauls wrote:
>
> +1 Sling Starter works for me.
>
> regards,
>
> Karl
>
> On Wednesday, October 4, 2017, Carsten Ziegeler
> On 4. Oct 2017, at 09:57, Robert Munteanu wrote:
>
> On Tue, 2017-10-03 at 17:03 +0200, Konrad Windszus wrote:
>>> On 3. Oct 2017, at 16:35, Bertrand Delacretaz >> rg> wrote:
>>>
>>> Hi,
>>>
>>> On Tue, Oct 3, 2017 at 3:50 PM, Konrad Windszus
Robert Munteanu wrote> On Tue, 2017-10-03 at 11:52 +0200, Carsten
Ziegeler wrote:
>>> 2. Reading the section on configuration merging, it is not clear to
>>> me
>>> if merging is merging of values or overriding of values.
>>>
>>> Consider
>>>
>>>
>>> feature 1:
>>>
>>> com.foo.bar.Service
>>>
[
https://issues.apache.org/jira/browse/SLING-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16190945#comment-16190945
]
Carsten Ziegeler commented on SLING-7152:
-
[~asanso] logout is only called if the user hits the
On Tue, 2017-10-03 at 11:52 +0200, Carsten Ziegeler wrote:
> > 2. Reading the section on configuration merging, it is not clear to
> > me
> > if merging is merging of values or overriding of values.
> >
> > Consider
> >
> >
> > feature 1:
> >
> > com.foo.bar.Service
> >prop1="A"
> >
On Tue, 2017-10-03 at 17:03 +0200, Konrad Windszus wrote:
> > On 3. Oct 2017, at 16:35, Bertrand Delacretaz > rg> wrote:
> >
> > Hi,
> >
> > On Tue, Oct 3, 2017 at 3:50 PM, Konrad Windszus
> > wrote:
> > > ...I think we also once discussed on the mailing
On Wed, 2017-10-04 at 00:53 +0200, Karl Pauls wrote:
> On Mon, Oct 2, 2017 at 10:17 PM, Robert Munteanu
> wrote:
> > Hi,
> >
> > I think that our samples could do with a little more usability.
> > They
> > are fine as code samples, but sometimes fail short when trying them
>
+1 Sling Starter works for me.
regards,
Karl
On Wednesday, October 4, 2017, Carsten Ziegeler
wrote:
> I like Starter as well (and agree that quickstart would be nice but we
> shouldn't use it due to the mentioned problems)
>
> So this would be Sling Starter as the basic
Thanks Bertrand,
I've added some variables for min java, min maven and Sling release version.
Regards
Carsten
Bertrand Delacretaz wrote
>> On Mon, Oct 2, 2017 at 5:10 PM, Robert Munteanu wrote:
>>> ...By reading the discussion at [1] it seems that we have to implement
>>>
Hi Eugen,
On Tue, 2017-10-03 at 16:38 +0300, Ioan Eugen Stan wrote:
> Hi,
>
> Great idea. How about Sling Starter/ Loader / Bootstrap ?
>
>
> Regarding building a real app with Spring I would like to go through
Ahem
s/Spring/Sling/ I assume :-)
> that process (be a guinee pig). We would
I like Starter as well (and agree that quickstart would be nice but we
shouldn't use it due to the mentioned problems)
So this would be Sling Starter as the basic name, Sling Starter
Application for our jar and Sling Starter Web Application.
Sounds good to me.
Regards
Carsten
Robert Munteanu
On Wed, 2017-10-04 at 00:43 +0200, Karl Pauls wrote:
> On Tue, Oct 3, 2017 at 4:37 PM, Bertrand Delacretaz
> wrote:
> > On Tue, Oct 3, 2017 at 3:58 PM, Konrad Windszus
> > wrote:
> > > ..."Sling Reference Distribution"
> >
> > I like that, and the
On Wed, 2017-10-04 at 08:34 +0200, Bertrand Delacretaz wrote:
> Hi,
>
> On Sat, Sep 30, 2017 at 12:09 PM, Carsten Ziegeler org> wrote:
> > ...This would keep our main page fairly short and we just need to
> > improve
> > the introduction "Sling in 100 words"..
>
> Here's my
Hi,
On Sat, Sep 30, 2017 at 12:09 PM, Carsten Ziegeler wrote:
> ...This would keep our main page fairly short and we just need to improve
> the introduction "Sling in 100 words"..
Here's my draft, feel free to tweak:
Apache Sling is a REST-based Web framework based on a
74 matches
Mail list logo