RE: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Stefan Seifert]

congratulations and good choice!

stefan

>-Original Message-
>From: Carsten Ziegeler [mailto:cziege...@apache.org]
>Sent: Thursday, November 16, 2017 3:25 PM
>To: Sling Developers; us...@sling.apache.org
>Subject: [ANN] New Apache Sling PMC Chair: Robert Munteanu
>
>Hi,
>
>it's my pleasure to announce that Robert took up the role as our new PMC
>chair.
>
>Congrats Robert!
>
>Regards
>Carsten
>--
>Carsten Ziegeler
>Adobe Research Switzerland
>cziege...@apache.org

[jira] [Commented] (SLING-7242) [Shiny] Sling Website Design

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16256600#comment-16256600
 ] 

Stefan Seifert commented on SLING-7242:
---

like it as well - if the header image would be a bit smaller. i'm also 
interested in an example of a sub page, and how the navigation structure looks 
like if you are e.g. in the 2nd, 3rd etc. level.

> [Shiny] Sling Website Design
> 
>
> Key: SLING-7242
> URL: https://issues.apache.org/jira/browse/SLING-7242
> Project: Sling
>  Issue Type: Task
>Reporter: Chris Millar
>Priority: Minor
> Attachments: Web 1920 – 1.png, browser-comparison.jpg
>
>
> As part of SLING-, it was mentioned the Sling website needs a re-design 
> to help attract new developers and make the site easier to use on mobile 
> devices.
> Now that the site is on JBake, it probably makes sense to start working on 
> this.
> The attached mockup is an initial take on the homepage. It's not meant to be 
> all-encompassing, but should provide a view into what the site could look 
> like and how it could match the new Sling Launchpad design.
> *Notes*
> * The image is pulled from Adobe Stock. Hopefully this can be donated, or we 
> can pull from the community to get an image we want to use. Was thinking 
> "greenfield" and not overly distracting.
> * I was looking for something punchy for the title text. "Effortlessly build 
> resource-driven web-applications." is what I came up with.
> * About text has been un-touched.
> * Easy build instructions are right on the homepage. Docker first, with Java 
> just a tab click away. This follows Docker now being the priority on the 
> getting started page.
> * News, Get Involved, and Additional Resource should be mostly 
> self-explanatory.
> * The navigation is designed around the common areas of the current left hand 
> rail, but with tutorials being broken out. This is a result of the many devs 
> I've on-boarded that prefer walk-throughs over raw docs.
> Overall the idea is to give a single page of the main topics, but kick out to 
> the pages already established.
> Let me know your thoughts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Is anyone looking into org.apache.sling.portal.container?

[Carsten Ziegeler]

I didn't even know we have such a cache module :)

I don't think we should move the portal stuff out of the whiteboard, I
would rather move the cache to the whiteboard as well.

Carsten


Robert Munteanu wrote
> Hi,
> 
> We have a persistent build failure for the commons-cache-portal job:
> 
> https://builds.apache.org/view/S-Z/view/Sling-Dashboard/job/sling-org-a
> pache-sling-commons-cache-portal-1.8/3/console
> 
> It is looking for an org.apache.sling.portal.container artifact which I
> can't find:
> 
> [ERROR] Failed to execute goal on project
> org.apache.sling.commons.cache.portal: Could not resolve dependencies
> for project
> org.apache.sling:org.apache.sling.commons.cache.portal:bundle:0.1-
> SNAPSHOT: Could not find artifact
> org.apache.sling.portal:org.apache.sling.portal.container:jar:0.6.0-
> SNAPSHOT in Nexus (http://repository.apache.org/snapshots) -> [Help 1]
> 
> It's not on Maven central, it's not on the ASF Nexus, it's only present
> in the SVN whiteboard
> 
> https://svn.apache.org/repos/asf/sling/whiteboard/portal/
> 
> This being present in the whiteboard it does not make a lot of sense to
> have an official module depend on it. The way I see it we either retire
> the commons-cache portal bundle or move the portal stuff from the
> whiteboard to our git repos.
> 
> Thoughts?
> 
> Thanks,
> 
> Robert
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Is anyone looking into org.apache.sling.portal.container?

[Robert Munteanu]

Hi,

We have a persistent build failure for the commons-cache-portal job:

https://builds.apache.org/view/S-Z/view/Sling-Dashboard/job/sling-org-a
pache-sling-commons-cache-portal-1.8/3/console

It is looking for an org.apache.sling.portal.container artifact which I
can't find:

[ERROR] Failed to execute goal on project
org.apache.sling.commons.cache.portal: Could not resolve dependencies
for project
org.apache.sling:org.apache.sling.commons.cache.portal:bundle:0.1-
SNAPSHOT: Could not find artifact
org.apache.sling.portal:org.apache.sling.portal.container:jar:0.6.0-
SNAPSHOT in Nexus (http://repository.apache.org/snapshots) -> [Help 1]

It's not on Maven central, it's not on the ASF Nexus, it's only present
in the SVN whiteboard

https://svn.apache.org/repos/asf/sling/whiteboard/portal/

This being present in the whiteboard it does not make a lot of sense to
have an official module depend on it. The way I see it we either retire
the commons-cache portal bundle or move the portal stuff from the
whiteboard to our git repos.

Thoughts?

Thanks,

Robert

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Robert Munteanu]

On Thu, 2017-11-16 at 06:25 -0800, Carsten Ziegeler wrote:
> Hi,
> 
> it's my pleasure to announce that Robert took up the role as our new
> PMC
> chair.

Thank you, Carsten, for having served as the PMC chair (literally) for
ages.

Thanks all for the kind words, I am looking forward to keeping working
with Sling. And hopefully no SCM migrations in the next 5 years :-)

Robert

Re: [VOTE] Release Apache Sling JCR Resource 3.0.8 and File System ClassLoader 1.0.8

[Carsten Ziegeler]

+1


Karl Pauls wrote
> I would like to call a vote on the following release,
> 
> Apache Sling JCR Resource 3.0.8
> 
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12342185
> 
> Apache Sling File System ClassLoader 1.0.8
> 
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12339771
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1814/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1814 /tmp/sling-staging
> 
> Please vote to approve these releases:
> 
>   [ ] +1 Approve the releases
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Roy Teeuwen]

Congratulations Robert!

Greets,
Roy

> On 16 Nov 2017, at 15:25, Carsten Ziegeler  wrote:
> 
> Hi,
> 
> it's my pleasure to announce that Robert took up the role as our new PMC
> chair.
> 
> Congrats Robert!
> 
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org



signature.asc
Description: Message signed with OpenPGP

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Timothee Maret]

Congrats Robert!

Regards,

Timothee

2017-11-16 15:25 GMT+01:00 Carsten Ziegeler :

> Hi,
>
> it's my pleasure to announce that Robert took up the role as our new PMC
> chair.
>
> Congrats Robert!
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [VOTE] Release Apache Sling JCR Davex 1.3.10

[Karl Pauls]

On Thu, Nov 16, 2017 at 3:54 PM, Julian Reschke  wrote:
> On 2017-11-16 13:07, Karl Pauls wrote:
>>
>> I would like to call a vote on the following release,
>>
>> Apache Sling JCR Davex 1.3.10
>> ...
>
>
> I'm about to branch Jackrabbit 2.16 and release 2.16.0 subsequently - so
> this seems to be minimally bad timing :-).

Oh well, no harm done. I missed SLING-7212 because it didn't have the
fixVersion set.

Anyways, this release will conclude before 2.16 is out - hence, I'll
added JCR Davex 1.3.12 to the fixVersion so that we don't forget.

regards,

Karl

-- 
Karl Pauls
karlpa...@gmail.com

[jira] [Updated] (SLING-7212) Update WebDAV servlets to Jackrabbit 2.16.0

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-7212:
--
Fix Version/s: JCR Davex 1.3.12
   JCR Webdav 2.3.10

> Update WebDAV servlets to Jackrabbit 2.16.0
> ---
>
> Key: SLING-7212
> URL: https://issues.apache.org/jira/browse/SLING-7212
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Affects Versions: JCR Davex 1.3.8, JCR Webdav 2.3.8
>Reporter: Julian Reschke
>Priority: Minor
> Fix For: JCR Webdav 2.3.10, JCR Davex 1.3.12
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Sling JCR Davex 1.3.10

[Julian Reschke]

On 2017-11-16 13:07, Karl Pauls wrote:

I would like to call a vote on the following release,

Apache Sling JCR Davex 1.3.10
...


I'm about to branch Jackrabbit 2.16 and release 2.16.0 subsequently - so 
this seems to be minimally bad timing :-).

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Bertrand Delacretaz]

On Thu, Nov 16, 2017 at 3:25 PM, Carsten Ziegeler  wrote:
> ...it's my pleasure to announce that Robert took up the role as our new PMC
> chair

Congrats Robert and thank you for taking up this job!

And many thanks Carsten for several years of service!

-Bertrand

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Antonio Sanso]

+1
On Nov 16, 2017, at 3:27 PM, Karl Pauls  wrote:

> +1
> 
> Congrats Robert!
> 
> regards,
> 
> Karl
> 
> On Thu, Nov 16, 2017 at 3:25 PM, Carsten Ziegeler  
> wrote:
>> Hi,
>> 
>> it's my pleasure to announce that Robert took up the role as our new PMC
>> chair.
>> 
>> Congrats Robert!
>> 
>> Regards
>> Carsten
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziege...@apache.org
> 
> 
> 
> -- 
> Karl Pauls
> karlpa...@gmail.com

[VOTE] Release Apache Sling JCR Resource 3.0.8 and File System ClassLoader 1.0.8

[Karl Pauls]

I would like to call a vote on the following release,

Apache Sling JCR Resource 3.0.8

We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12342185

Apache Sling File System ClassLoader 1.0.8

We solved 2 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12339771

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1814/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1814 /tmp/sling-staging

Please vote to approve these releases:

  [ ] +1 Approve the releases
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

[jira] [Resolved] (SLING-6419) Remove loginAdministrative() usage from jcr.resource - JcrSystemUserValidator

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls resolved SLING-6419.
---
Resolution: Fixed

I merged the PR with some more commenting and using 'validation' for the 
service user name.

> Remove loginAdministrative() usage from jcr.resource - JcrSystemUserValidator
> -
>
> Key: SLING-6419
> URL: https://issues.apache.org/jira/browse/SLING-6419
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Antonio Sanso
>Assignee: Karl Pauls
> Fix For: JCR Resource 3.0.8
>
>
> Remove getAdministrativeResourceResolver() and loginAdministrative() usage 
> from jcr.resource



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6419) Remove loginAdministrative() usage from jcr.resource - JcrSystemUserValidator

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255412#comment-16255412
 ] 

ASF GitHub Bot commented on SLING-6419:
---

karlpauls closed pull request #1: SLING-6419: Switch JcrSystemUserValidator to 
a service user 
URL: https://github.com/apache/sling-org-apache-sling-jcr-resource/pull/1
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Remove loginAdministrative() usage from jcr.resource - JcrSystemUserValidator
> -
>
> Key: SLING-6419
> URL: https://issues.apache.org/jira/browse/SLING-6419
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Antonio Sanso
>Assignee: Karl Pauls
> Fix For: JCR Resource 3.0.8
>
>
> Remove getAdministrativeResourceResolver() and loginAdministrative() usage 
> from jcr.resource



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Nicolas Peltier]

congrats Robert!

2017-11-16 15:25 GMT+01:00 Carsten Ziegeler :
> Hi,
>
> it's my pleasure to announce that Robert took up the role as our new PMC
> chair.
>
> Congrats Robert!
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

Re: [ANN] New Apache Sling PMC Chair: Robert Munteanu

[Karl Pauls]

+1

Congrats Robert!

regards,

Karl

On Thu, Nov 16, 2017 at 3:25 PM, Carsten Ziegeler  wrote:
> Hi,
>
> it's my pleasure to announce that Robert took up the role as our new PMC
> chair.
>
> Congrats Robert!
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org



-- 
Karl Pauls
karlpa...@gmail.com

[ANN] New Apache Sling PMC Chair: Robert Munteanu

[Carsten Ziegeler]

Hi,

it's my pleasure to announce that Robert took up the role as our new PMC
chair.

Congrats Robert!

Regards
Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling JCR Davex 1.3.10

[Carsten Ziegeler]

+1


Karl Pauls wrote
> I would like to call a vote on the following release,
> 
> Apache Sling JCR Davex 1.3.10
> 
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12339343
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1813/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1813 /tmp/sling-staging
> 
> Please vote to approve these releases:
> 
>   [ ] +1 Approve the releases
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Security 1.1.8

[Karl Pauls]

+1

regards,

Karl

On Thu, Nov 16, 2017 at 3:00 PM, Antonio Sanso  wrote:
> +1
> On Nov 15, 2017, at 2:20 PM, Antonio Sanso  wrote:
>
>> Hi,
>>
>> We solved 2 issues in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12341288
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1811/
>>
>> You can use this UNIX script to download the release and verify the 
>> signatures:
>> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 1811 /tmp/sling-staging
>>
>> Please vote to approve this release:
>>
>>  [ ] +1 Approve the release
>>  [ ]  0 Don't care
>>  [ ] -1 Don't release, because ...
>>
>> This majority vote is open for at least 72 hours.
>



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Health Check API 1.0.2, Health Check Core 1.2.10, and Health Check Annotations 1.0.6

[Carsten Ziegeler]

+1


Karl Pauls wrote
> I would like to call a vote on the following releases,
> 
> Apache Sling Health Check API 1.0.2
> 
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12340564
> 
> Apache Sling Health Check Core 1.2.10
> 
> We solved 5 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12340563
> 
> Apache Sling Health Check Annotations 1.0.6
> 
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12335063
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1812/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1812 /tmp/sling-staging
> 
> Please vote to approve these releases:
> 
>   [ ] +1 Approve the releases
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Security 1.1.8

[Antonio Sanso]

+1
On Nov 15, 2017, at 2:20 PM, Antonio Sanso  wrote:

> Hi,
> 
> We solved 2 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341288
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1811/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1811 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
> 
> This majority vote is open for at least 72 hours.

Re: [VOTE] Release Apache Sling JCR Davex 1.3.10

[Stefan Egli]

+1

Cheers,
Stefan

On 16.11.17, 13:07, "Karl Pauls"  wrote:

>I would like to call a vote on the following release,
>
>Apache Sling JCR Davex 1.3.10
>
>We solved 2 issue in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12339343
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1813/
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1813 /tmp/sling-staging
>
>Please vote to approve these releases:
>
>  [ ] +1 Approve the releases
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...

Re: [VOTE] Release Apache Sling Security 1.1.8

[Stefan Egli]

+1

Cheers,
Stefan

On 15.11.17, 14:20, "Antonio Sanso"  wrote:

>Hi,
>
>We solved 2 issues in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12341288
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1811/
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1811 /tmp/sling-staging
>
>Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
>This majority vote is open for at least 72 hours.

Re: [VOTE] Release Apache Sling Health Check API 1.0.2, Health Check Core 1.2.10, and Health Check Annotations 1.0.6

[Stefan Egli]

+1

Cheers,
Stefan

On 16.11.17, 12:57, "Karl Pauls"  wrote:

>I would like to call a vote on the following releases,
>
>Apache Sling Health Check API 1.0.2
>
>We solved 2 issue in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12340564
>
>Apache Sling Health Check Core 1.2.10
>
>We solved 5 issue in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12340563
>
>Apache Sling Health Check Annotations 1.0.6
>
>We solved 1 issue in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12335063
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1812/
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1812 /tmp/sling-staging
>
>Please vote to approve these releases:
>
>  [ ] +1 Approve the releases
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...

Re: [VOTE] Release Apache Sling Launchpad Base 5.6.10-2.6.26

[Stefan Egli]

+1

Cheers,
Stefan

On 14.11.17, 23:21, "Karl Pauls"  wrote:

>I would like to call a vote on the following release,
>
>Apache Sling Launchpad Base 5.6.10-2.6.26
>
>We solved 2 issue in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12341546
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1810/
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1810 /tmp/sling-staging
>
>Please vote to approve these releases:
>
>  [ ] +1 Approve the releases
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...

Re: [VOTE] Release Apache Sling JCR Davex 1.3.10

[Antonio Sanso]

+1
On Nov 16, 2017, at 1:07 PM, Karl Pauls  wrote:

> I would like to call a vote on the following release,
> 
> Apache Sling JCR Davex 1.3.10
> 
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12339343
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1813/
> 
> You can use this UNIX script to download the release and verify the 
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1813 /tmp/sling-staging
> 
> Please vote to approve these releases:
> 
>  [ ] +1 Approve the releases
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...

[VOTE] Release Apache Sling JCR Davex 1.3.10

[Karl Pauls]

I would like to call a vote on the following release,

Apache Sling JCR Davex 1.3.10

We solved 2 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12339343

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1813/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1813 /tmp/sling-staging

Please vote to approve these releases:

  [ ] +1 Approve the releases
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

[jira] [Updated] (SLING-7157) metatype.properties file must not be in OSGI-INF/metatype

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-7157:
--
Fix Version/s: (was: JCR Davex 1.3.10)
   JCR Davex 1.3.12

> metatype.properties file must not be in OSGI-INF/metatype
> -
>
> Key: SLING-7157
> URL: https://issues.apache.org/jira/browse/SLING-7157
> Project: Sling
>  Issue Type: Bug
>Affects Versions: JCR Web Console 1.0.2, JCR Registration 1.0.2, JCR 
> ClassLoader 3.2.2, Form Based Authentication 1.0.8, Settings 1.3.8, Commons 
> Threads 3.2.6, Auth Core 1.4.0, SLF4J MDC Filter 1.0.0, Authentication XING 
> OAuth 0.0.2, Authentication XING Login 0.0.2, URL Rewriter 0.0.2, DataSource 
> Provider 1.0.4, NoSQL MongoDB Resource Provider 1.1.0, Commons Log 5.0.2, 
> Discovery Impl 1.2.12, Discovery Oak 1.2.18, JCR Davex 1.3.8, JCR Webdav 
> 2.3.8, JCR Installer 3.1.26
>Reporter: Carsten Ziegeler
>Priority: Blocker
> Fix For: JCR Web Console 1.0.4, JCR Registration 1.0.4, JCR 
> ClassLoader 3.2.4, Form Based Authentication 1.0.10, Settings 1.3.10, Auth 
> Core 1.4.2, Mongo Resource Provider 1.0.0, Authentication XING OAuth 0.0.4, 
> Authentication XING Login 0.0.4, DataSource Provider 1.0.4, URL Rewriter 
> 0.0.4, Commons Log 5.0.4, Commons Threads 3.2.10, SLF4J MDC Filter 1.0.2, JCR 
> Webdav 2.3.10, JCR Installer 3.1.28, Discovery Impl 1.2.14, Discovery Oak 
> 1.2.24, JCR Davex 1.3.12
>
>
> According to the spec the metatype.properties file must not be inside the 
> OSGI-INF/metatype directory. This is against the spec, so we should move it 
> to OSGI-INF/l10n
> We probably should also upgrade the maven-scr-plugin for this 1.25.0
> I found the following files:
> ./bundles/auth/core/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/auth/form/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/commons/log/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/commons/threads/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/extensions/discovery/impl/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/extensions/discovery/oak/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/extensions/settings/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/jcr/classloader/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/jcr/davex/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/jcr/registration/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/jcr/webconsole/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./bundles/jcr/webdav/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/auth/org.apache.sling.auth.xing.login/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/auth/org.apache.sling.auth.xing.oauth/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/extensions/datasource/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/extensions/mongodb/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/extensions/slf4j-mdc/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/extensions/startup-filter/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./contrib/extensions/urlrewriter/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./installer/providers/jcr/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./samples/path-based-rtp/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./samples/workspacepicker/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./testing/junit/core/src/main/resources/OSGI-INF/metatype/metatype.properties
> ./testing/junit/healthcheck/src/main/resources/OSGI-INF/metatype/metatype.properties



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[VOTE] Release Apache Sling Health Check API 1.0.2, Health Check Core 1.2.10, and Health Check Annotations 1.0.6

[Karl Pauls]

I would like to call a vote on the following releases,

Apache Sling Health Check API 1.0.2

We solved 2 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12340564

Apache Sling Health Check Core 1.2.10

We solved 5 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12340563

Apache Sling Health Check Annotations 1.0.6

We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12335063

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1812/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1812 /tmp/sling-staging

Please vote to approve these releases:

  [ ] +1 Approve the releases
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

[jira] [Commented] (SLING-6855) Sticky Results Support

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255151#comment-16255151
 ] 

Karl Pauls commented on SLING-6855:
---

[~henzlerg], I'm resolving this issue as the code has been commited. Please 
follow-up on the documentation using SLING-7246.

> Sticky Results Support
> --
>
> Key: SLING-6855
> URL: https://issues.apache.org/jira/browse/SLING-6855
> Project: Sling
>  Issue Type: New Feature
>  Components: Health Check
>Reporter: Clinton H Goudie-Nice
>Assignee: Georg Henzler
> Fix For: Health Check Annotations 1.0.6, Health Check Core 
> 1.2.10, Health Check API 1.0.2
>
>
> Introduce HC service property {{hc.warningsStickForMinutes}} to allow old 
> WARN/CRITICAL/HEALTH_CHECK_ERROR results to be sticky (see also 
> http://sling.markmail.org/thread/tawikgt7bqxvnlj5#query:+page:1+mid:57hhg55hekr7ib33+state:results)
> --- Original Request 
> *Create ResultRegistry to provide health check behavior for executing code 
> that does not want a HealthCheck* 
> I want to provide a Registry service that can be leveraged to provide health 
> check results.
> These results can be for a period of time through an expiration, until the 
> JVM is restarted, or added and later removed.
> This can be useful when code observes a specific (possibly bad) state, and 
> wants to alert through the health check API that this state has taken place.
>  Some examples: 
>  An event pool has filled, and some events will be thrown away.
>   This is a failure case that requires a restart of the instance.
>   It would be appropriate to trigger a permanent failure.
>
>  A quota has been tripped. This quota may immediately recover, but it is 
> sensible to alert for 30 minutes that the quota has been tripped.
>  If you expect the failure will clear itself within a certain window, setting 
> the expiration to that window can be ideal.
> GHPR to follow



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-6946) Make HC servlet send CORS header Access-Control-Allow-Origin

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255150#comment-16255150
 ] 

Karl Pauls commented on SLING-6946:
---

[~henzlerg], I'm resolving this issue as the code has been commited. Please 
follow-up on the documentation using SLING-7246.

> Make HC servlet send CORS header Access-Control-Allow-Origin
> 
>
> Key: SLING-6946
> URL: https://issues.apache.org/jira/browse/SLING-6946
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
> Fix For: Health Check Core 1.2.10
>
>
> There is no reason why the HC servlet should not be allowed to be called from 
> a webpage that was served from another domain. Hence the header 
> {{Access-Control-Allow-Origin}} shall be added with a default value {{*}} 
> (configurable in case it is really needed, but allowing general access as 
> default makes sense here).
> Concrete Use Case: A Jenkins HTML Report that aggregates HC results from 
> multiple sling instances.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7246) Document changes for SLING-6855 and SLING-6946

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-7246:
--
Description: Moving out the pending documentation for SLING-6855 and 
SLING-6946 to this issue. [~henzlerg], please follow-up wrt. the missing 
documentation (if any) using this issue.  (was: Moving out the pending 
documentation for SLING-6855 to this issue. [~henzlerg], please follow-up wrt. 
the missing documentation (if any) using this issue).)

> Document changes for SLING-6855 and SLING-6946
> --
>
> Key: SLING-7246
> URL: https://issues.apache.org/jira/browse/SLING-7246
> Project: Sling
>  Issue Type: Task
>  Components: Health Check
>Reporter: Karl Pauls
>Assignee: Georg Henzler
> Fix For: Health Check Core 1.2.12
>
>
> Moving out the pending documentation for SLING-6855 and SLING-6946 to this 
> issue. [~henzlerg], please follow-up wrt. the missing documentation (if any) 
> using this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7246) Document changes for SLING-6855 and SLING-6946

[Karl Pauls (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated SLING-7246:
--
Summary: Document changes for SLING-6855 and SLING-6946  (was: Document 
changes for Sticky Results Support in SLING-6855)

> Document changes for SLING-6855 and SLING-6946
> --
>
> Key: SLING-7246
> URL: https://issues.apache.org/jira/browse/SLING-7246
> Project: Sling
>  Issue Type: Task
>  Components: Health Check
>Reporter: Karl Pauls
>Assignee: Georg Henzler
> Fix For: Health Check Core 1.2.12
>
>
> Moving out the pending documentation for SLING-6855 to this issue. 
> [~henzlerg], please follow-up wrt. the missing documentation (if any) using 
> this issue).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7246) Document changes for Sticky Results Support in SLING-6855

[Karl Pauls (JIRA)]

Karl Pauls created SLING-7246:
-

 Summary: Document changes for Sticky Results Support in SLING-6855
 Key: SLING-7246
 URL: https://issues.apache.org/jira/browse/SLING-7246
 Project: Sling
  Issue Type: Task
  Components: Health Check
Reporter: Karl Pauls
Assignee: Georg Henzler
 Fix For: Health Check Core 1.2.12


Moving out the pending documentation for SLING-6855 to this issue. [~henzlerg], 
please follow-up wrt. the missing documentation (if any) using this issue).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7241) [pipes] Nashorn ScriptEngine in PipeBindings is null

[Nicolas Peltier (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255107#comment-16255107
 ] 

Nicolas Peltier commented on SLING-7241:


[~karlpauls] that's not noise, it's fine enriching this ticket with your 
lights. 

[~bcsott] i'm fine merging in your change, but with some comment explaining 
that parameter as said (pls amend your commit and push --force so you have only 
one commit)
thanks!

> [pipes] Nashorn ScriptEngine in PipeBindings is null
> 
>
> Key: SLING-7241
> URL: https://issues.apache.org/jira/browse/SLING-7241
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 1.0.4
> Environment: java.runtime.name = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
>Reporter: Björn Csott
>Priority: Minor
> Attachments: error.log
>
>
> Under some unclear circumstances the ScriptEngine in PipeBindings does not 
> get initialized.
> There is a solution out there to attach Nashorn to the system bundle. Appart 
> from that I was able to fix it by using a different constructor: 
> ScriptEngineManager(null). 
> The issue can be reproduced by deploying 
> https://github.com/bcsott/migration-tool
> When it fails the following is written to stderror.log:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (SLING-7161) Update site to reference git instead of svn

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255096#comment-16255096
 ] 

Bertrand Delacretaz edited comment on SLING-7161 at 11/16/17 10:37 AM:
---

> ...inconsistent spacing in Groovy templates (sometimes tabs, sometimes 
> spaces)...

Totally my fault, I used a mix of editors when working on those, including some 
badly configured ones :-\

I suggest that we fix files when we need to touch them, ideally with separate 
formatting-only commits.

Suggest using tabs as we do in other places.


was (Author: bdelacretaz):
> ...inconsistent spacing in Groovy templates (sometimes tabs, sometimes 
> spaces)...

Totally my fault, I used a mix of editors when working on those, including some 
badly configured ones :-\

I suggest that we fix files when we need to touch them, ideally with separate 
formatting-only commits.

> Update site to reference git instead of svn
> ---
>
> Key: SLING-7161
> URL: https://issues.apache.org/jira/browse/SLING-7161
> Project: Sling
>  Issue Type: Sub-task
>  Components: Site
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> All the https://svn.apache.org/repos/asf/sling/... tags should be rewritten 
> to the git repos.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7161) Update site to reference git instead of svn

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255096#comment-16255096
 ] 

Bertrand Delacretaz commented on SLING-7161:


> ...inconsistent spacing in Groovy templates (sometimes tabs, sometimes 
> spaces)...

Totally my fault, I used a mix of editors when working on those, including some 
badly configured ones :-\

I suggest that we fix files when we need to touch them, ideally with separate 
formatting-only commits.

> Update site to reference git instead of svn
> ---
>
> Key: SLING-7161
> URL: https://issues.apache.org/jira/browse/SLING-7161
> Project: Sling
>  Issue Type: Sub-task
>  Components: Site
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>
> All the https://svn.apache.org/repos/asf/sling/... tags should be rewritten 
> to the git repos.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7241) [pipes] Nashorn ScriptEngine in PipeBindings is null

[Karl Pauls (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255053#comment-16255053
 ] 

Karl Pauls commented on SLING-7241:
---

[~bcsott], oh sorry - I see now that you are talking about using the 
ScriptEngineManager directly. I was assuming this would use the sling 
scriptengine. [~npeltier], in that case, I agree, while this is related to 
problems in SLING-7134 it will not be addressed directly. Sorry for the noice. 

[~bcsott], I think the difference you see is due to a ThreadContextClassloader. 
Probably that is set to something different in the JMX case as in the others 
(maybe worthwhile to figure out what the ThreadContextClassloader is set to in 
each case).

> [pipes] Nashorn ScriptEngine in PipeBindings is null
> 
>
> Key: SLING-7241
> URL: https://issues.apache.org/jira/browse/SLING-7241
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 1.0.4
> Environment: java.runtime.name = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
>Reporter: Björn Csott
>Priority: Minor
> Attachments: error.log
>
>
> Under some unclear circumstances the ScriptEngine in PipeBindings does not 
> get initialized.
> There is a solution out there to attach Nashorn to the system bundle. Appart 
> from that I was able to fix it by using a different constructor: 
> ScriptEngineManager(null). 
> The issue can be reproduced by deploying 
> https://github.com/bcsott/migration-tool
> When it fails the following is written to stderror.log:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7242) [Shiny] Sling Website Design

[Julian Sedding (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255035#comment-16255035
 ] 

Julian Sedding commented on SLING-7242:
---

[~auniverseaway] You're right, I haven't been looking at 100% zoom. The font 
size is fine for me, maybe the headings are a little on the large side ;)

> [Shiny] Sling Website Design
> 
>
> Key: SLING-7242
> URL: https://issues.apache.org/jira/browse/SLING-7242
> Project: Sling
>  Issue Type: Task
>Reporter: Chris Millar
>Priority: Minor
> Attachments: Web 1920 – 1.png, browser-comparison.jpg
>
>
> As part of SLING-, it was mentioned the Sling website needs a re-design 
> to help attract new developers and make the site easier to use on mobile 
> devices.
> Now that the site is on JBake, it probably makes sense to start working on 
> this.
> The attached mockup is an initial take on the homepage. It's not meant to be 
> all-encompassing, but should provide a view into what the site could look 
> like and how it could match the new Sling Launchpad design.
> *Notes*
> * The image is pulled from Adobe Stock. Hopefully this can be donated, or we 
> can pull from the community to get an image we want to use. Was thinking 
> "greenfield" and not overly distracting.
> * I was looking for something punchy for the title text. "Effortlessly build 
> resource-driven web-applications." is what I came up with.
> * About text has been un-touched.
> * Easy build instructions are right on the homepage. Docker first, with Java 
> just a tab click away. This follows Docker now being the priority on the 
> getting started page.
> * News, Get Involved, and Additional Resource should be mostly 
> self-explanatory.
> * The navigation is designed around the common areas of the current left hand 
> rail, but with tutorials being broken out. This is a result of the many devs 
> I've on-boarded that prefer walk-throughs over raw docs.
> Overall the idea is to give a single page of the main topics, but kick out to 
> the pages already established.
> Let me know your thoughts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7241) [pipes] Nashorn ScriptEngine in PipeBindings is null

[JIRA]

[ 
https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254980#comment-16254980
 ] 

Björn Csott commented on SLING-7241:


[~npeltier], I was debugging several solutions. Using the PlumberServlet via 
curl always works. So I started to investigate whats the difference. I added 
the  which was the only missing piece in 
my bundle.

The result of my investigation was:
* Copy of Plumber Servlet in my Bundle -> does not work
* Plumber in Service called from Servlet -> does not work
* Plumber in Service executed via JMX -> works
* Plumber in Servlet ->does not work

No difference on Mac or Windows. Also tried several JVM versions. No difference.
The only stable solution I found (besides adding Nashorn to system bundle) is 
using the other constructor. I think 
https://issues.apache.org/jira/browse/SLING-7134?focusedCommentId=16187822=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16187822
 describes also this strange behavior.

> [pipes] Nashorn ScriptEngine in PipeBindings is null
> 
>
> Key: SLING-7241
> URL: https://issues.apache.org/jira/browse/SLING-7241
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Pipes 1.0.4
> Environment: java.runtime.name = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
>Reporter: Björn Csott
>Priority: Minor
> Attachments: error.log
>
>
> Under some unclear circumstances the ScriptEngine in PipeBindings does not 
> get initialized.
> There is a solution out there to attach Nashorn to the system bundle. Appart 
> from that I was able to fix it by using a different constructor: 
> ScriptEngineManager(null). 
> The issue can be reproduced by deploying 
> https://github.com/bcsott/migration-tool
> When it fails the following is written to stderror.log:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)