[jira] [Resolved] (SLING-7459) Official endpoints property from Http Whiteboard should be used

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-7459.
-
Resolution: Fixed

Fixed in rev ae2b304

> Official endpoints property from Http Whiteboard should be used
> ---
>
> Key: SLING-7459
> URL: https://issues.apache.org/jira/browse/SLING-7459
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Discovery Base 2.0.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Discovery Base 2.0.6
>
>
> Currently the implementation uses the interims property 
> "osgi.http.service.endpoints" from the RFC. The final http whiteboard spec 
> however changed that name to "osgi.http.endpoints".
> Therefore we should use the official name (and revert back to the interims 
> one if not found)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7459) Official endpoints property from Http Whiteboard should be used

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-7459:
---

 Summary: Official endpoints property from Http Whiteboard should 
be used
 Key: SLING-7459
 URL: https://issues.apache.org/jira/browse/SLING-7459
 Project: Sling
  Issue Type: Bug
  Components: Commons
Affects Versions: Discovery Base 2.0.4
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: Discovery Base 2.0.6


Currently the implementation uses the interims property 
"osgi.http.service.endpoints" from the RFC. The final http whiteboard spec 
however changed that name to "osgi.http.endpoints".

Therefore we should use the official name (and revert back to the interims one 
if not found)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7458) Index Out of Bounds in sling:getParents Tag / Function

[Dan Klco (JIRA)]

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

Dan Klco updated SLING-7458:

Fix Version/s: (was: Scripting JSP-Taglib 2.2.8)
   Scripting JSP Taglib 2.2.8

> Index Out of Bounds in sling:getParents Tag / Function
> --
>
> Key: SLING-7458
> URL: https://issues.apache.org/jira/browse/SLING-7458
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting JSP-Taglib 2.2.6
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Minor
> Fix For: Scripting JSP Taglib 2.2.8
>
>
> If the user specifies a depth greater than the depth of the resource used for 
> the child note, the  sling:getParents Tag and Function will throw an Index 
> Out of Bounds exception. The less-error prone behavior would be to return an 
> empty iterator of parent resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7040) Update commons lang 2.x to 3.5

[Dan Klco (JIRA)]

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

Dan Klco updated SLING-7040:

Fix Version/s: (was: Scripting JSP-Taglib 2.2.8)
   Scripting JSP Taglib 2.2.8

> Update commons lang 2.x to 3.5
> --
>
> Key: SLING-7040
> URL: https://issues.apache.org/jira/browse/SLING-7040
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR, Scripting
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Scripting Core 2.0.48, Resource Collections 1.0.2, 
> Scripting HTL JS Use Provider 1.0.22, Scripting HTL Engine 1.0.38, Scripting 
> HTL Compiler 1.0.10, Scripting HTL Java Compiler 1.0.10, Sling Models Impl 
> 1.4.4, Health Check Core 1.2.10, JCR ContentLoader 2.2.4, Scripting JSP 
> Taglib 2.2.8
>
>
> In some modules we're still using the old commons lang 2.x version; we should 
> update to the maintained 3.x version



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7448) New Sling Tags for Retrieving Resource Parents

[Dan Klco (JIRA)]

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

Dan Klco resolved SLING-7448.
-
Resolution: Fixed

> New Sling Tags for Retrieving Resource Parents
> --
>
> Key: SLING-7448
> URL: https://issues.apache.org/jira/browse/SLING-7448
> Project: Sling
>  Issue Type: Improvement
>Affects Versions: Scripting JSP Taglib 2.2.6
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Major
> Fix For: Scripting JSP Taglib 2.2.8
>
>
> Currently, it's difficult to work with parent Resources via JSP tags. Two 
> useful tags / EL Functions would be:
>  * GetParents - get the parents of a resource in depth order optionally 
> starting at a certain depth
>  * GetParent - gets the parent of a resource at a specified depth



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7458) Index Out of Bounds in sling:getParents Tag / Function

[Dan Klco (JIRA)]

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

Dan Klco reassigned SLING-7458:
---

Assignee: Dan Klco

> Index Out of Bounds in sling:getParents Tag / Function
> --
>
> Key: SLING-7458
> URL: https://issues.apache.org/jira/browse/SLING-7458
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting JSP-Taglib 2.2.6
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Minor
> Fix For: Scripting JSP-Taglib 2.2.8
>
>
> If the user specifies a depth greater than the depth of the resource used for 
> the child note, the  sling:getParents Tag and Function will throw an Index 
> Out of Bounds exception. The less-error prone behavior would be to return an 
> empty iterator of parent resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7458) Index Out of Bounds in sling:getParents Tag / Function

[Dan Klco (JIRA)]

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

Dan Klco resolved SLING-7458.
-
Resolution: Fixed

Fixed in 
https://github.com/apache/sling-org-apache-sling-scripting-jsp-taglib/commit/463596ca6a2436636ab762ddad1795b30e6dc91f

> Index Out of Bounds in sling:getParents Tag / Function
> --
>
> Key: SLING-7458
> URL: https://issues.apache.org/jira/browse/SLING-7458
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Scripting JSP-Taglib 2.2.6
>Reporter: Dan Klco
>Priority: Minor
> Fix For: Scripting JSP-Taglib 2.2.8
>
>
> If the user specifies a depth greater than the depth of the resource used for 
> the child note, the  sling:getParents Tag and Function will throw an Index 
> Out of Bounds exception. The less-error prone behavior would be to return an 
> empty iterator of parent resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7458) Index Out of Bounds in sling:getParents Tag / Function

[Dan Klco (JIRA)]

Dan Klco created SLING-7458:
---

 Summary: Index Out of Bounds in sling:getParents Tag / Function
 Key: SLING-7458
 URL: https://issues.apache.org/jira/browse/SLING-7458
 Project: Sling
  Issue Type: Bug
Affects Versions: Scripting JSP-Taglib 2.2.6
Reporter: Dan Klco
 Fix For: Scripting JSP-Taglib 2.2.8


If the user specifies a depth greater than the depth of the resource used for 
the child note, the  sling:getParents Tag and Function will throw an Index Out 
of Bounds exception. The less-error prone behavior would be to return an empty 
iterator of parent resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7457:
-

The [NoSQL Resource 
Providers|https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
 and the related Launchpad are not providing a JCR itself – so don't use them. 
Use [Sling Starter|https://github.com/apache/sling-org-apache-sling-starter] 10 
with run mode {{oak_mongo}} if you prefer Mongo over TAR (btw, you can also run 
Sling with 
[Oak/RDBMS|https://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html]).

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in setting it up and it works as I thought, seems to be a very 
> valuable product for those who want to rapidlly build a software that relies 
> on JCR, which is my case.
> But the next question is "Should I use a noSQL Database or not". As it may be 
> an important choice, since Sling is not really compatible with SQL database, 
> I wanted to make sling run with MongoDB.
> I read the documentation, and at first impression, it seemed quite immediate; 
> I simply have to add an option to change the mode of launching the starter 
> application, as it is said in the following documentation: 
> [https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]
>  
> So I tried to launch the starter application with the following lines:
> java -Dsling.run.modes=oak,oak_mongo -jar 
> org.apache.sling.starter-10-SNAPSHOT.jar
> and checked with a mongodb client if a mongodb server was started or not ...
> As I was unable to connect to mongodb://localhost:27017 I guess something is 
> missing, maybe mongodb should be installed separetely ? 
>  
> I continue reading the documentation, and find 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
> OK, my conclusion was I missed to install the nosql-resource-providers, so I 
> installed the bundle and check again ...
> Nothing new, it seems I have done nothing.
> So, always according to 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,]
>  there is another launchpad to use.
> There is the link to the source code: 
> https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad
> But it is said that this source repository is obsolete and shall not be used.
> So I get back to apache git repository, and filtered on "sling" and "nosql", 
> I can find some code now ...
> https://github.com/apache?utf8=%E2%9C%93=sling+nosql==
> But it is absolutely not clear to me whether I have to do something with that 
> modules or not ...
> So my real problem is I can't get the right documentation on "How to setup 
> Sling 9 to work with mongodb" and there is, as far as I know, no forum where 
> I can ask this to a community to help.
> I guess sling is working well with mongoDB, but if I need 10 days to set it 
> up (I spend 1 day, maybe it is not enough) my point of view is made: I won't 
> use mongodb.
> But this maybe a terrible mistake !
>  
> So help please !
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[frederic rougeot (JIRA)]

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

frederic rougeot edited comment on SLING-7457 at 1/31/18 5:06 PM:
--

I tried first with OAk Segment Tar and it is OK for me.

The next step was using MongoDB.

I said in previous comment It was OK now, but in fact not...

I checked that the sling database is created in mongodb, it was OK and I 
thought everything was fine.

But when accessing to http:/localhost:8080 I got now the following HTTP 403 
error...

Once again, I think the documentation should help !

I guess I have to provide somewhere the right configuration for authenticating 
to the mongodb database ... 

 
h1. Forbidden (403)

The requested URL resulted in an error in 
org.apache.sling.servlets.get.DefaultGetServlet.
h3. Request Progress:

0 TIMER_START\{Request Processing} 0 COMMENT timer_end format is \{,}  0 LOG Method=GET, PathInfo= 0 
TIMER_START\{ResourceResolution} 2 TIMER_END\{2,ResourceResolution} URI= 
resolves to Resource=NoSqlResource, type=nt:unstructured, superType=null, 
path=/ 2 LOG Resource Path Info: SlingRequestPathInfo: path='/', 
selectorString='null', extension='null', suffix='null' 2 
TIMER_START\{ServletResolution} 2 TIMER_START\{resolveServlet(NoSqlResource, 
type=nt:unstructured, superType=null, path=/)} 2 
TIMER_END\{0,resolveServlet(NoSqlResource, type=nt:unstructured, 
superType=null, path=/)} Using servlet 
org.apache.sling.servlets.get.DefaultGetServlet 2 
TIMER_END\{0,ServletResolution} URI= handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet 3 LOG Applying 
Requestfilters 3 LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter 3 LOG 
Calling filter: org.apache.sling.i18n.impl.I18NFilter 3 LOG Applying 
Componentfilters 3 
TIMER_START\{org.apache.sling.servlets.get.DefaultGetServlet#0} 3 LOG Using 
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for 
extension=null 5 LOG Applying Error filters 5 LOG Calling filter: 
org.apache.sling.i18n.impl.I18NFilter 5 TIMER_START\{handleError:status=403} 40 
TIMER_END\{35,handleError:status=403} Using handler 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet 
41 TIMER_END\{41,Request Processing} Dumping SlingRequestProgressTracker Entries


was (Author: frougeot):
I tried first with OAk Segment Tar and it is OK for me.

The next step was using MongoDB.

I said in previous comment It was OK now, but it is not the case right now ...

I checked that the sling database is created in mongodb, it is OK and I thought 
everything was fine.

But now I got the following HTTP 403 ... when accessing to http:/localhost:8080 
just to see how sling react now it is linked with mongodb ...

Once again, I think the documentation should help !

 
h1. Forbidden (403)

The requested URL resulted in an error in 
org.apache.sling.servlets.get.DefaultGetServlet.
h3. Request Progress:

0 TIMER_START\{Request Processing} 0 COMMENT timer_end format is \{,}  0 LOG Method=GET, PathInfo= 0 
TIMER_START\{ResourceResolution} 2 TIMER_END\{2,ResourceResolution} URI= 
resolves to Resource=NoSqlResource, type=nt:unstructured, superType=null, 
path=/ 2 LOG Resource Path Info: SlingRequestPathInfo: path='/', 
selectorString='null', extension='null', suffix='null' 2 
TIMER_START\{ServletResolution} 2 TIMER_START\{resolveServlet(NoSqlResource, 
type=nt:unstructured, superType=null, path=/)} 2 
TIMER_END\{0,resolveServlet(NoSqlResource, type=nt:unstructured, 
superType=null, path=/)} Using servlet 
org.apache.sling.servlets.get.DefaultGetServlet 2 
TIMER_END\{0,ServletResolution} URI= handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet 3 LOG Applying 
Requestfilters 3 LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter 3 LOG 
Calling filter: org.apache.sling.i18n.impl.I18NFilter 3 LOG Applying 
Componentfilters 3 
TIMER_START\{org.apache.sling.servlets.get.DefaultGetServlet#0} 3 LOG Using 
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for 
extension=null 5 LOG Applying Error filters 5 LOG Calling filter: 
org.apache.sling.i18n.impl.I18NFilter 5 TIMER_START\{handleError:status=403} 40 
TIMER_END\{35,handleError:status=403} Using handler 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet 
41 TIMER_END\{41,Request Processing} Dumping SlingRequestProgressTracker Entries

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in 

[jira] [Commented] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[frederic rougeot (JIRA)]

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

frederic rougeot commented on SLING-7457:
-

I tried first with OAk Segment Tar and it is OK for me.

The next step was using MongoDB.

I said in previous comment It was OK now, but it is not the case right now ...

I checked that the sling database is created in mongodb, it is OK and I thought 
everything was fine.

But now I got the following HTTP 403 ... when accessing to http:/localhost:8080 
just to see how sling react now it is linked with mongodb ...

Once again, I think the documentation should help !

 
h1. Forbidden (403)

The requested URL resulted in an error in 
org.apache.sling.servlets.get.DefaultGetServlet.
h3. Request Progress:

0 TIMER_START\{Request Processing} 0 COMMENT timer_end format is \{,}  0 LOG Method=GET, PathInfo= 0 
TIMER_START\{ResourceResolution} 2 TIMER_END\{2,ResourceResolution} URI= 
resolves to Resource=NoSqlResource, type=nt:unstructured, superType=null, 
path=/ 2 LOG Resource Path Info: SlingRequestPathInfo: path='/', 
selectorString='null', extension='null', suffix='null' 2 
TIMER_START\{ServletResolution} 2 TIMER_START\{resolveServlet(NoSqlResource, 
type=nt:unstructured, superType=null, path=/)} 2 
TIMER_END\{0,resolveServlet(NoSqlResource, type=nt:unstructured, 
superType=null, path=/)} Using servlet 
org.apache.sling.servlets.get.DefaultGetServlet 2 
TIMER_END\{0,ServletResolution} URI= handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet 3 LOG Applying 
Requestfilters 3 LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter 3 LOG 
Calling filter: org.apache.sling.i18n.impl.I18NFilter 3 LOG Applying 
Componentfilters 3 
TIMER_START\{org.apache.sling.servlets.get.DefaultGetServlet#0} 3 LOG Using 
org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for 
extension=null 5 LOG Applying Error filters 5 LOG Calling filter: 
org.apache.sling.i18n.impl.I18NFilter 5 TIMER_START\{handleError:status=403} 40 
TIMER_END\{35,handleError:status=403} Using handler 
org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet 
41 TIMER_END\{41,Request Processing} Dumping SlingRequestProgressTracker Entries

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in setting it up and it works as I thought, seems to be a very 
> valuable product for those who want to rapidlly build a software that relies 
> on JCR, which is my case.
> But the next question is "Should I use a noSQL Database or not". As it may be 
> an important choice, since Sling is not really compatible with SQL database, 
> I wanted to make sling run with MongoDB.
> I read the documentation, and at first impression, it seemed quite immediate; 
> I simply have to add an option to change the mode of launching the starter 
> application, as it is said in the following documentation: 
> [https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]
>  
> So I tried to launch the starter application with the following lines:
> java -Dsling.run.modes=oak,oak_mongo -jar 
> org.apache.sling.starter-10-SNAPSHOT.jar
> and checked with a mongodb client if a mongodb server was started or not ...
> As I was unable to connect to mongodb://localhost:27017 I guess something is 
> missing, maybe mongodb should be installed separetely ? 
>  
> I continue reading the documentation, and find 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
> OK, my conclusion was I missed to install the nosql-resource-providers, so I 
> installed the bundle and check again ...
> Nothing new, it seems I have done nothing.
> So, always according to 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,]
>  there is another launchpad to use.
> There is the link to the source code: 
> https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad
> But it is said that this source repository is obsolete and shall not be used.
> So I get back to apache git repository, and filtered on "sling" and "nosql", 
> I can find some code now ...
> https://github.com/apache?utf8=%E2%9C%93=sling+nosql==
> But it is absolutely not clear to me whether I have to do something with that 
> modules or not ...
> So my real problem is I can't get the right documentation on "How to setup 
> Sling 9 to work with mongodb" and there is, as far as I know, no forum where 
> I can ask this to a community to help.
> I guess sling is working well with 

[jira] [Commented] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[frederic rougeot (JIRA)]

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

frederic rougeot commented on SLING-7457:
-

I succeed indeed, by providing a mongodb database by myself, and by using the 
launchpad dedicated to mongodb after building it, from the source code I got in 
the actual apache git repository not the deprecated one.

I really think the documentation is very confusing on that part.

 

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in setting it up and it works as I thought, seems to be a very 
> valuable product for those who want to rapidlly build a software that relies 
> on JCR, which is my case.
> But the next question is "Should I use a noSQL Database or not". As it may be 
> an important choice, since Sling is not really compatible with SQL database, 
> I wanted to make sling run with MongoDB.
> I read the documentation, and at first impression, it seemed quite immediate; 
> I simply have to add an option to change the mode of launching the starter 
> application, as it is said in the following documentation: 
> [https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]
>  
> So I tried to launch the starter application with the following lines:
> java -Dsling.run.modes=oak,oak_mongo -jar 
> org.apache.sling.starter-10-SNAPSHOT.jar
> and checked with a mongodb client if a mongodb server was started or not ...
> As I was unable to connect to mongodb://localhost:27017 I guess something is 
> missing, maybe mongodb should be installed separetely ? 
>  
> I continue reading the documentation, and find 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
> OK, my conclusion was I missed to install the nosql-resource-providers, so I 
> installed the bundle and check again ...
> Nothing new, it seems I have done nothing.
> So, always according to 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,]
>  there is another launchpad to use.
> There is the link to the source code: 
> https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad
> But it is said that this source repository is obsolete and shall not be used.
> So I get back to apache git repository, and filtered on "sling" and "nosql", 
> I can find some code now ...
> https://github.com/apache?utf8=%E2%9C%93=sling+nosql==
> But it is absolutely not clear to me whether I have to do something with that 
> modules or not ...
> So my real problem is I can't get the right documentation on "How to setup 
> Sling 9 to work with mongodb" and there is, as far as I know, no forum where 
> I can ask this to a community to help.
> I guess sling is working well with mongoDB, but if I need 10 days to set it 
> up (I spend 1 day, maybe it is not enough) my point of view is made: I won't 
> use mongodb.
> But this maybe a terrible mistake !
>  
> So help please !
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7457:
-

Sling with Oak Mongo requires a running MongoDB instance on localhost (port: 
{{27017}}, db: {{sling}}) – it's documented for 
[Karaf|https://sling.apache.org/documentation/karaf.html#getting-started], but 
we should improve documentation for Sling Starter.

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in setting it up and it works as I thought, seems to be a very 
> valuable product for those who want to rapidlly build a software that relies 
> on JCR, which is my case.
> But the next question is "Should I use a noSQL Database or not". As it may be 
> an important choice, since Sling is not really compatible with SQL database, 
> I wanted to make sling run with MongoDB.
> I read the documentation, and at first impression, it seemed quite immediate; 
> I simply have to add an option to change the mode of launching the starter 
> application, as it is said in the following documentation: 
> [https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]
>  
> So I tried to launch the starter application with the following lines:
> java -Dsling.run.modes=oak,oak_mongo -jar 
> org.apache.sling.starter-10-SNAPSHOT.jar
> and checked with a mongodb client if a mongodb server was started or not ...
> As I was unable to connect to mongodb://localhost:27017 I guess something is 
> missing, maybe mongodb should be installed separetely ? 
>  
> I continue reading the documentation, and find 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
> OK, my conclusion was I missed to install the nosql-resource-providers, so I 
> installed the bundle and check again ...
> Nothing new, it seems I have done nothing.
> So, always according to 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,]
>  there is another launchpad to use.
> There is the link to the source code: 
> https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad
> But it is said that this source repository is obsolete and shall not be used.
> So I get back to apache git repository, and filtered on "sling" and "nosql", 
> I can find some code now ...
> https://github.com/apache?utf8=%E2%9C%93=sling+nosql==
> But it is absolutely not clear to me whether I have to do something with that 
> modules or not ...
> So my real problem is I can't get the right documentation on "How to setup 
> Sling 9 to work with mongodb" and there is, as far as I know, no forum where 
> I can ask this to a community to help.
> I guess sling is working well with mongoDB, but if I need 10 days to set it 
> up (I spend 1 day, maybe it is not enough) my point of view is made: I won't 
> use mongodb.
> But this maybe a terrible mistake !
>  
> So help please !
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: apache/sling as github landing repository

[Bertrand Delacretaz]

On Wed, Jan 31, 2018 at 4:05 PM, Robert Munteanu  wrote:
> ...perhaps we should consider making the aggregator the 'sling'
> repository, explaining where the old links went in a README, and
> keeping 'sling-old-svn-mirror' without a redirect...

That would work for me.

As long as people find instructions to get, build and explore Sling
when they land at github.com/apache/sling I think we're fine.

-Bertrand

[jira] [Commented] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-7457:
-

Please try with Oak Segment Tar if you are new to Sling.

For help or discussions use our [mailings 
lists|https://sling.apache.org/project-information.html#mailing-lists].

> Poor documentation on mongoDB or other NOSQL use
> 
>
> Key: SLING-7457
> URL: https://issues.apache.org/jira/browse/SLING-7457
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: frederic rougeot
>Priority: Major
>
> I am evaluating sling.
> I succeed in setting it up and it works as I thought, seems to be a very 
> valuable product for those who want to rapidlly build a software that relies 
> on JCR, which is my case.
> But the next question is "Should I use a noSQL Database or not". As it may be 
> an important choice, since Sling is not really compatible with SQL database, 
> I wanted to make sling run with MongoDB.
> I read the documentation, and at first impression, it seemed quite immediate; 
> I simply have to add an option to change the mode of launching the starter 
> application, as it is said in the following documentation: 
> [https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]
>  
> So I tried to launch the starter application with the following lines:
> java -Dsling.run.modes=oak,oak_mongo -jar 
> org.apache.sling.starter-10-SNAPSHOT.jar
> and checked with a mongodb client if a mongodb server was started or not ...
> As I was unable to connect to mongodb://localhost:27017 I guess something is 
> missing, maybe mongodb should be installed separetely ? 
>  
> I continue reading the documentation, and find 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]
> OK, my conclusion was I missed to install the nosql-resource-providers, so I 
> installed the bundle and check again ...
> Nothing new, it seems I have done nothing.
> So, always according to 
> [https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,]
>  there is another launchpad to use.
> There is the link to the source code: 
> https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad
> But it is said that this source repository is obsolete and shall not be used.
> So I get back to apache git repository, and filtered on "sling" and "nosql", 
> I can find some code now ...
> https://github.com/apache?utf8=%E2%9C%93=sling+nosql==
> But it is absolutely not clear to me whether I have to do something with that 
> modules or not ...
> So my real problem is I can't get the right documentation on "How to setup 
> Sling 9 to work with mongodb" and there is, as far as I know, no forum where 
> I can ask this to a community to help.
> I guess sling is working well with mongoDB, but if I need 10 days to set it 
> up (I spend 1 day, maybe it is not enough) my point of view is made: I won't 
> use mongodb.
> But this maybe a terrible mistake !
>  
> So help please !
>  
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-7456:
---

I guess all of the handling of the cache seems to suffer a bit from possible 
race conditions. I'll not have time for this right now but we should try to 
clean that up a little.

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls reassigned SLING-7456:
-

Assignee: (was: Karl Pauls)

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7457) Poor documentation on mongoDB or other NOSQL use

[frederic rougeot (JIRA)]

frederic rougeot created SLING-7457:
---

 Summary: Poor documentation on mongoDB or other NOSQL use
 Key: SLING-7457
 URL: https://issues.apache.org/jira/browse/SLING-7457
 Project: Sling
  Issue Type: Bug
  Components: Documentation
Reporter: frederic rougeot


I am evaluating sling.

I succeed in setting it up and it works as I thought, seems to be a very 
valuable product for those who want to rapidlly build a software that relies on 
JCR, which is my case.

But the next question is "Should I use a noSQL Database or not". As it may be 
an important choice, since Sling is not really compatible with SQL database, I 
wanted to make sling run with MongoDB.

I read the documentation, and at first impression, it seemed quite immediate; I 
simply have to add an option to change the mode of launching the starter 
application, as it is said in the following documentation: 
[https://sling.apache.org/documentation/the-sling-engine/the-sling-launchpad.html]

 

So I tried to launch the starter application with the following lines:

java -Dsling.run.modes=oak,oak_mongo -jar 
org.apache.sling.starter-10-SNAPSHOT.jar

and checked with a mongodb client if a mongodb server was started or not ...

As I was unable to connect to mongodb://localhost:27017 I guess something is 
missing, maybe mongodb should be installed separetely ? 

 

I continue reading the documentation, and find 
[https://sling.apache.org/documentation/bundles/nosql-resource-providers.html]

OK, my conclusion was I missed to install the nosql-resource-providers, so I 
installed the bundle and check again ...

Nothing new, it seems I have done nothing.

So, always according to 
[https://sling.apache.org/documentation/bundles/nosql-resource-providers.html,] 
there is another launchpad to use.

There is the link to the source code: 
https://github.com/apache/sling-old-svn-mirror/tree/trunk/contrib/nosql/launchpad

But it is said that this source repository is obsolete and shall not be used.

So I get back to apache git repository, and filtered on "sling" and "nosql", I 
can find some code now ...

https://github.com/apache?utf8=%E2%9C%93=sling+nosql==

But it is absolutely not clear to me whether I have to do something with that 
modules or not ...

So my real problem is I can't get the right documentation on "How to setup 
Sling 9 to work with mongodb" and there is, as far as I know, no forum where I 
can ask this to a community to help.

I guess sling is working well with mongoDB, but if I need 10 days to set it up 
(I spend 1 day, maybe it is not enough) my point of view is made: I won't use 
mongodb.

But this maybe a terrible mistake !

 

So help please !

 

 

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls reassigned SLING-7456:
-

Assignee: Karl Pauls

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-7456:
---

[~cziegeler], ah right - I missed that. Yes, must have been a deactivate then.

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler edited comment on SLING-7456 at 1/31/18 3:13 PM:
--

[~karlpauls] The listener is only registered if cache is not null:

[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L865]

The check for the jmx bean at 
[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L879]
 should be changed

However in your stack trace, the listener is invoked. As that seems to be a 
scheduled thread, I assume the servlets resolver is already disposed (where 
cache has been set to null). So we should check for null in flush just to avoid 
this situation


was (Author: cziegeler):
[~karlpauls] The listener is only registered if cache is not null:

[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L865]

The check for the jmx bean at 
[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L879]
 should be changed

However in your stack trace, the listener is invoked, which according to the 
code can't happen

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-7456:
-

[~karlpauls] The listener is only registered if cache is not null:

[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L865]

The check for the jmx bean at 
[https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/main/java/org/apache/sling/servlets/resolver/internal/SlingServletResolver.java#L879]
 should be changed

However in your stack trace, the listener is invoked, which according to the 
code can't happen

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-7456:
---

[~cziegeler], not sure - it looks like we might not have a cache if the 
cachesize is configured to be > 5. Again, I'm not sure why this happend but it 
was in a messed up instance so maybe that had something going wrong in the 
configs and ended-up with a cachesize too small?

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: apache/sling as github landing repository

[Robert Munteanu]

On Wed, 2018-01-31 at 10:00 +0100, Bertrand Delacretaz wrote:
> Hi,
> 
> On Wed, Jan 31, 2018 at 9:23 AM, Robert Munteanu 
> wrote:
> > On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote:
> > > ... 4. add the aggregator and new landing page readme on the
> > > master
> > > branch, which will be push-able for committers...
> > > 
> > 
> > ...The only downside would be that
> > cloning the repository would be really slow due to the large
> > size
> 
> I think we need to have the aggregator [0] run a regular build to
> update the list of Git repositories, soon. That becomes more
> important
> as that list starts including tags, contrib/core/etc status and other
> metadata that will change more often than now.
> 
> I don't think a large Git repository is a good place for such an
> automatically built list of Git repositories metadata, as Jenkins
> would need to transfer lots of unneeded data, a dedicated small
> repository is much better for that. And I'm not sure right now how to
> push the output of that to any branch from builds.apache.org, at this
> point I only know how to commit to an asf-site branch (by tying the
> Jenkins build to build nodes having the git-websites label).

Then perhaps we should consider making the aggregator the 'sling'
repository, explaining where the old links went in a README, and
keeping 'sling-old-svn-mirror' without a redirect.

Also see the 'Sling docker image' thread [1], it seems keeping the main
repo read-only has some disadvantages we did not consider.

Robert

[1] https://lists.apache.org/thread.html/2b0f66c9d9a756bc574c233d9d0904
8713944b602d7292fb8001d69c@%3Cdev.sling.apache.org%3E

> 
> -Bertrand
> 
> > [0] https://github.com/apache/sling-aggregator - which needs a
> > Maven build to be automated

Sling docker image

[Robert Munteanu]

Hi,

Related to the ongoing github.com/apache/sling landing page discussion,
I'd like to discuss our docker setup.

Currently we provide an apachelsling/sling [1] image, which is OK. I
investigated setting up a build under the more official apache account,
but unfortunately the automated docker builds picks up the image name
from the repository, so we ended up with apache/sling-org-apache-sling-
starter-docker, which is quite ugly.

If we choose automated builds, getting back the 'sling' repository is
something we should consider.

Thanks,

Robert

[1]: https://hub.docker.com/r/apachesling/sling/
[2]: https://hub.docker.com/r/apache/sling-org-apache-sling-starter-doc
ker/

Re: [VOTE] Release Apache Sling Repoinit Parser 1.2.2 and Repoinit JCR 1.1.8

[Robert Munteanu]

On Wed, 2018-01-31 at 14:38 +0100, Karl Pauls wrote:
> Please vote to approve these releases:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[jira] [Commented] (SLING-7456) FlushCache in SlingServletResolver can throw an NPE

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-7456:
-

This is interesting, the resolver is only registered as an event receiver if 
the cache is not null.

However if the jmx bean is invoked, there should be a null check nevertheless.

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 3)

[Carsten Ziegeler]

+1


Robert Munteanu wrote
> Hi,
> 
> Update note: I've chosen to respin the Starter release a second time
> with the same version, for 2 reasons:
> 
> - it would generate confusion to skip a release
> - chances of anyone depending on the staged slingstart are slim
> 
> If anyone thinks otherwise, I'll restart the release vote as Sling 11.
> 
> 
> Time to release Sling 10. This year I've added all the testing
> projects, to retain what was working at the time of the release and the
> archetypes, to allow users to start using the new features immediately
> rather than releasing them separately.
> 
> This has lead to a rather large release though.
> 
> The following artifacts, with the associated changelogs, are included
> in this release
> 
> - Apache Sling Starter 10
> https://issues.apache.org/jira/projects/SLING/versions/12340941 (13
> issues)
> 
> - Apache Sling Launchpad Testing 10
> https://issues.apache.org/jira/projects/SLING/versions/12317575 (33
> issues)
> 
> - Apache Sling Launchpad Testing WAR 10
> https://issues.apache.org/jira/projects/SLING/versions/12342164 (0
> issues)
> 
> - Apache Sling Launchpad Integration Tests 1.0.6
> https://issues.apache.org/jira/projects/SLING/versions/12341715 (0
> issues)
> 
> - Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
> - Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)
> 
> - Apache Sling Launchpad Testing Services 2.0.14
> https://issues.apache.org/jira/projects/SLING/versions/12338823 (2
> issues)
> 
> - Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)
> 
> - Apache Sling Archetype Parent 5
> https://issues.apache.org/jira/projects/SLING/versions/12333898 (2
> issues)
> 
> - Apache Sling Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2
> issues)
> 
> - Apache Sling JCRInstall Bundle Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2
> issues)
> 
> - Apache Sling Initial Content Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2
> issues)
> 
> - Apache Sling Slingstart Archetype 1.0.6
> https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2
> issues)
> 
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachesling-1857
> https://repository.apache.org/content/repositories/orgapachesling-1868
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;
> f=check_staged_release.sh;hb=HEAD
> 
> Usage:
> sh check_staged_release.sh 1857 /tmp/sling-stagingsh
> sh check_staged_release.sh 1868 /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, but I'd be more than
> happy to allow extensions if anyone needs more time to validate the
> release.
> 
> Thanks,
> 
> Robert
> 
> 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [VOTE] Release Apache Sling Repoinit Parser 1.2.2 and Repoinit JCR 1.1.8

[Carsten Ziegeler]

+1


Karl Pauls wrote
> I would like to call a vote on the following releases,
> 
> Apache Sling Repoinit Parser 1.2.2
> 
> We solved 3 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341653
> 
> Apache Sling Repoinit JCR 1.1.8
> 
> We solved 5 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341654
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1867/
> 
> 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 1867 /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 Repoinit Parser 1.2.2 and Repoinit JCR 1.1.8

[Bertrand Delacretaz]

On Wed, Jan 31, 2018 at 2:38 PM, Karl Pauls  wrote:
> ...Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1867/ ...

+1 for the release of

SHA1(org.apache.sling.jcr.repoinit-1.1.8-source-release.zip)=
64ca994e0936ba54ec192f2fc243672c3cdc7089

SHA1(org.apache.sling.repoinit.parser-1.2.2-source-release.zip)=
3ecd9d71811555731320d51a7bb6b5452e5dc941

Checked signatures, digests and build.

-Bertrand

[VOTE] Release Apache Sling Starter 10 + associated testing projects and archetypes (take 3)

[Robert Munteanu]

Hi,

Update note: I've chosen to respin the Starter release a second time
with the same version, for 2 reasons:

- it would generate confusion to skip a release
- chances of anyone depending on the staged slingstart are slim

If anyone thinks otherwise, I'll restart the release vote as Sling 11.


Time to release Sling 10. This year I've added all the testing
projects, to retain what was working at the time of the release and the
archetypes, to allow users to start using the new features immediately
rather than releasing them separately.

This has lead to a rather large release though.

The following artifacts, with the associated changelogs, are included
in this release

- Apache Sling Starter 10
https://issues.apache.org/jira/projects/SLING/versions/12340941 (13
issues)

- Apache Sling Launchpad Testing 10
https://issues.apache.org/jira/projects/SLING/versions/12317575 (33
issues)

- Apache Sling Launchpad Testing WAR 10
https://issues.apache.org/jira/projects/SLING/versions/12342164 (0
issues)

- Apache Sling Launchpad Integration Tests 1.0.6
https://issues.apache.org/jira/projects/SLING/versions/12341715 (0
issues)

- Apache Sling Launchpad Test Bundles 0.0.4 (no changelog)
- Apache Sling Launchpad Testing Fragment Bundle 2.0.14 (no changelog)

- Apache Sling Launchpad Testing Services 2.0.14
https://issues.apache.org/jira/projects/SLING/versions/12338823 (2
issues)

- Apache Sling Launchpad Testing Services WAR 2.0.14 (no changelog)

- Apache Sling Archetype Parent 5
https://issues.apache.org/jira/projects/SLING/versions/12333898 (2
issues)

- Apache Sling Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333900 (2
issues)

- Apache Sling JCRInstall Bundle Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333901 (2
issues)

- Apache Sling Initial Content Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12333902 (2
issues)

- Apache Sling Slingstart Archetype 1.0.6
https://issues.apache.org/jira/browse/SLING/fixforversion/12340954 (2
issues)

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

You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;
f=check_staged_release.sh;hb=HEAD

Usage:
sh check_staged_release.sh 1857 /tmp/sling-stagingsh
sh check_staged_release.sh 1868 /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, but I'd be more than
happy to allow extensions if anyone needs more time to validate the
release.

Thanks,

Robert

[VOTE] Release Apache Sling Repoinit Parser 1.2.2 and Repoinit JCR 1.1.8

[Karl Pauls]

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

Apache Sling Repoinit Parser 1.2.2

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

Apache Sling Repoinit JCR 1.1.8

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

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

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 1867 /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-7456) FlushCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

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

Karl Pauls updated SLING-7456:
--
Summary: FlushCache in SlingServletResolver can throw an NPE  (was: 
FluchCache in SlingServletResolver can throw an NPE)

> FlushCache in SlingServletResolver can throw an NPE
> ---
>
> Key: SLING-7456
> URL: https://issues.apache.org/jira/browse/SLING-7456
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Servlets Resolver 2.4.24
>
>
> Given that we check for the this.cache being null everytime we reference the 
> cache we should probably do the same in flushCache. I can't reproduce it but 
> the NPE looked like this:
> {noformat}
> java.lang.NullPointerException: null
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
>  [org.apache.sling.servlets.resolver:2.4.22]
>   at 
> org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
>  [org.apache.sling.resourceresolver:1.5.34]
>   at 
> org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
>  [org.apache.sling.jcr.resource:3.0.8]
>   at 
> org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
>  [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
>   at 
> org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
>  [org.apache.jackrabbit.oak-jcr:1.8.1]
>   at 
> org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
>  [org.apache.jackrabbit.oak-core:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at 
> org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
>  [org.apache.jackrabbit.oak-store-spi:1.8.1]
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
>   at java.base/java.lang.Thread.run(Thread.java:844)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7456) FluchCache in SlingServletResolver can throw an NPE

[Karl Pauls (JIRA)]

Karl Pauls created SLING-7456:
-

 Summary: FluchCache in SlingServletResolver can throw an NPE
 Key: SLING-7456
 URL: https://issues.apache.org/jira/browse/SLING-7456
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Resolver 2.4.22
Reporter: Karl Pauls
 Fix For: Servlets Resolver 2.4.24


Given that we check for the this.cache being null everytime we reference the 
cache we should probably do the same in flushCache. I can't reproduce it but 
the NPE looked like this:
{noformat}
java.lang.NullPointerException: null
at 
org.apache.sling.servlets.resolver.internal.SlingServletResolver.flushCache(SlingServletResolver.java:1122)
 [org.apache.sling.servlets.resolver:2.4.22]
at 
org.apache.sling.servlets.resolver.internal.SlingServletResolver.onChange(SlingServletResolver.java:1464)
 [org.apache.sling.servlets.resolver:2.4.22]
at 
org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges(BasicObservationReporter.java:211)
 [org.apache.sling.resourceresolver:1.5.34]
at 
org.apache.sling.jcr.resource.internal.JcrResourceListener.onEvent(JcrResourceListener.java:155)
 [org.apache.sling.jcr.resource:3.0.8]
at 
org.apache.jackrabbit.commons.observation.ListenerTracker$1.onEvent(ListenerTracker.java:190)
 [org.apache.jackrabbit.jackrabbit-jcr-commons:2.16.0]
at 
org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor.contentChanged(ChangeProcessor.java:508)
 [org.apache.jackrabbit.oak-jcr:1.8.1]
at 
org.apache.jackrabbit.oak.plugins.observation.FilteringDispatcher.contentChanged(FilteringDispatcher.java:53)
 [org.apache.jackrabbit.oak-core:1.8.1]
at 
org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:128)
 [org.apache.jackrabbit.oak-store-spi:1.8.1]
at 
org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:122)
 [org.apache.jackrabbit.oak-store-spi:1.8.1]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.base/java.lang.Thread.run(Thread.java:844)
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[RESULT] [VOTE] Release Apache Sling Thread Support 3.2.16

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Oliver Lietz, Konrad Windszus, Karl Pauls, Carsten
Ziegeler

I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

Thanks for voting.

Robert

[jira] [Commented] (SLING-7455) Provide a way to restrict access to servlets and scripts (jsp/ecma etc.)

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-7455:


[~nitin.nizhawan] - I sense there is a larger discussion lurking here :-) I 
suggest you write an email to dev@sling.apache.org, discussing your proposal

> Provide a way to restrict access to servlets and scripts (jsp/ecma etc.)
> 
>
> Key: SLING-7455
> URL: https://issues.apache.org/jira/browse/SLING-7455
> Project: Sling
>  Issue Type: New Feature
>  Components: Resource Access Security, Servlets
>Affects Versions: Servlets Resolver 2.4.22
>Reporter: Nitin Nizhawan
>Priority: Critical
>
> *Issue*
> Most of the web servers provide a way to restrict access to urls based on 
> roles/groups of users. Also, since mapping of urls and scripts (servlets/jsp) 
> is internal and end user cannot define this mapping, this method effectively 
> restricts access to scripts (servlets/jsp).
>  
> On the other hand, sling restricts access to end point using ACLs setup of 
> content nodes having sling:resourceType property set in the repository. i.e. 
> nodes which have "sling:resourceType" set can be used to invoke script 
> identified by value of "sling:resourceType" property by a user only if she 
> also has read permission on the node
>  
> But as we know that mapping of paths and scripts(servlets/jsp) is done via 
> "sling:resourceType" property and since this property can written by end 
> users having write access to the repository using SlingPostServlet or 
> possibly other tools.
> Which means that any user having read/write access to any part of repository 
> can invoke, any servlet or script by creating a node with sling:resourceType 
> property with its value set to resourceType of desired script/servlet. 
> Although, the scripts which make use of current user session are not 
> particularly affected by this since permission checks would be done by 
> repository layer once this scripts access/modify content using this session.
> But many scripts which either use service user (thus un-linking repository 
> permission check from current users session) or scripts which may have 
> nothing to do with repository such as contacting an external service, crypto, 
> filesystem access, launching processes etc. have no way to restrict access 
> other than manually checking in code for session permissions etc.)
>  
> *Expected*
> A  declarative method to restrict access to scripts (servlet/jsp). 
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SLING-7455) Provide a way to restrict access to servlets and scripts (jsp/ecma etc.)

[Nitin Nizhawan (JIRA)]

Nitin Nizhawan created SLING-7455:
-

 Summary: Provide a way to restrict access to servlets and scripts 
(jsp/ecma etc.)
 Key: SLING-7455
 URL: https://issues.apache.org/jira/browse/SLING-7455
 Project: Sling
  Issue Type: New Feature
  Components: Resource Access Security, Servlets
Affects Versions: Servlets Resolver 2.4.22
Reporter: Nitin Nizhawan


*Issue*

Most of the web servers provide a way to restrict access to urls based on 
roles/groups of users. Also, since mapping of urls and scripts (servlets/jsp) 
is internal and end user cannot define this mapping, this method effectively 
restricts access to scripts (servlets/jsp).

 

On the other hand, sling restricts access to end point using ACLs setup of 
content nodes having sling:resourceType property set in the repository. i.e. 
nodes which have "sling:resourceType" set can be used to invoke script 
identified by value of "sling:resourceType" property by a user only if she also 
has read permission on the node

 

But as we know that mapping of paths and scripts(servlets/jsp) is done via 
"sling:resourceType" property and since this property can written by end users 
having write access to the repository using SlingPostServlet or possibly other 
tools.

Which means that any user having read/write access to any part of repository 
can invoke, any servlet or script by creating a node with sling:resourceType 
property with its value set to resourceType of desired script/servlet. 

Although, the scripts which make use of current user session are not 
particularly affected by this since permission checks would be done by 
repository layer once this scripts access/modify content using this session.

But many scripts which either use service user (thus un-linking repository 
permission check from current users session) or scripts which may have nothing 
to do with repository such as contacting an external service, crypto, 
filesystem access, launching processes etc. have no way to restrict access 
other than manually checking in code for session permissions etc.)



 

*Expected*

A  declarative method to restrict access to scripts (servlet/jsp). 

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7454) Move repoinit integration tests to the JCR repoinit module

[ASF GitHub Bot (JIRA)]

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

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

karlpauls closed pull request #3: SLING-7454: Make the IT use the latest 
repoinit snapshots, enable dis…
URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/3
 
 
   


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


> Move repoinit integration tests to the JCR repoinit module
> --
>
> Key: SLING-7454
> URL: https://issues.apache.org/jira/browse/SLING-7454
> Project: Sling
>  Issue Type: Task
>  Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.6
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Repoinit JCR 1.1.8
>
>
> Currently those tests are at 
> [https://github.com/apache/sling-org-apache-sling-repoinit-it] and they are 
> failing.
> It makes more sense anyway to move them to the jcr-repoinit module which has 
> similar dependencies, and in that way they are executed at the right time, 
> before releasing that module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (SLING-7454) Move repoinit integration tests to the JCR repoinit module

[Karl Pauls (JIRA)]

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

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

Done

> Move repoinit integration tests to the JCR repoinit module
> --
>
> Key: SLING-7454
> URL: https://issues.apache.org/jira/browse/SLING-7454
> Project: Sling
>  Issue Type: Task
>  Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.6
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Repoinit JCR 1.1.8
>
>
> Currently those tests are at 
> [https://github.com/apache/sling-org-apache-sling-repoinit-it] and they are 
> failing.
> It makes more sense anyway to move them to the jcr-repoinit module which has 
> similar dependencies, and in that way they are executed at the right time, 
> before releasing that module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SLING-7454) Move repoinit integration tests to the JCR repoinit module

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-7454:


Thank you [~karlpauls], looks good to me! {{usePomDependencies}} is what I was 
missing, I see it now in the 
[https://sling.apache.org/components/slingstart-maven-plugin/prepare-package-mojo.html]
 docs.

+1 for merging and releasing.

> Move repoinit integration tests to the JCR repoinit module
> --
>
> Key: SLING-7454
> URL: https://issues.apache.org/jira/browse/SLING-7454
> Project: Sling
>  Issue Type: Task
>  Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.6
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Repoinit JCR 1.1.8
>
>
> Currently those tests are at 
> [https://github.com/apache/sling-org-apache-sling-repoinit-it] and they are 
> failing.
> It makes more sense anyway to move them to the jcr-repoinit module which has 
> similar dependencies, and in that way they are executed at the right time, 
> before releasing that module.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Generating Repo manifest, Maven "build all" pom, Jenkins jobs and repolist.html - a summary of the current state

[Bertrand Delacretaz]

Hi,

I had a look at the various initiatives around that in the last few
days and wrote a summary of (my understanding of) the current state.

It's at https://issues.apache.org/jira/browse/SLING-7262, feedback is
welcome and feel free to comment there for things that I missed.

-Bertrand

[jira] [Comment Edited] (SLING-7262) Generate reusable lists of Git repositories for machine consumption

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz edited comment on SLING-7262 at 1/31/18 10:26 AM:
--

Trying to summarize the various initiatives going on, as well as our 
requirements, please correct/complete as needed.

*Inputs*
 * Either the GitHub API to list all Sling repositories as currently used at 
[https://github.com/apache/sling-aggregator]
 * Or the Gitbox OPML at [https://gitbox.apache.org/repos/asf?a=opml] as 
currently used by [https://github.com/oliverlietz/apache-sling-aggregator]

*Desired Outputs*
 * 1) A manifest for the Google Repo tool, which requires just the repository 
names and their paths.
 * 2) Our Jenkins jobs, currently generated manually by running scripts from 
https://github.com/apache/sling-tooling-jenkins
 * 3) A list suitable for updating [http://sling.apache.org/repolist.html] (or 
a similar canonical Web page)
 * 4) A Maven reactor pom that allows for building everything or sets of 
modules, probably based on Maven profiles

For 1) I haven't checked if the Repo manifest format officially allows us to 
add extra information, currently we have an additional "groups" attribute, if 
that's supported we might add "tags", "badges" and "descriptions" as needed.

For 3) the repositories need to be grouped by functional areas (already 
partially done) and should also have tags or badges for contrib/core/legacy and 
similar classifications. It would be nice to have a brief description of each 
repository as well in that list, maybe the first few lines of their README 
(excluding "belongs to Apache Sling" of course)

*Environment*
 The generation of these files needs to run as a Jenkins build so that they can 
be regenerated automatically.

Commiting the output of Jenkins jobs to Git is easy if the target is the 
{{asf-site}} branch, for that we just need to tie the jobs to nodes having the 
{{git-websites}} label. Committing the output to the {{asf-site}} branch of the 
[https://github.com/apache/sling-site] repository seems to be a good solution 
to me and other scripts can pick it up there at a stable URL, even if the raw 
result is not visible on the website.

*Here's what we currently have "in production"*
 * [https://github.com/apache/sling-aggregator] generates a Repo manifest, 
needs to be updated manually by running a script and pushing the result when 
new Git repos are created
 * [http://sling.apache.org/repolist.html] is generated from that Repo 
manifest. It's missing tags/badges and descriptions
 * Our Jenkins jobs are generated from 
[https://github.com/apache/sling-tooling-jenkins] and optionally use 
information from a {{.sling-module.xml}} file described at 
[https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor]
 * I don't think we have an official Maven aggregator pom at this point
 * [~olli] has been working on 
[https://github.com/oliverlietz/apache-sling-aggregator] with useful things in 
various branches of that repository, which generate a Repo manifest, a Maven 
pom and a GitHub page.

See 
[https://github.com/apache/sling-org-apache-sling-launchpad-contrib-testing] 
for an example of a sling:contrib badge that can easily be parsed from the 
README and is displayed there, as opposed to {{.sling-module.xml}} which has no 
impact on the README page on GitHub:
{code:java}
curl -s 
https://raw.githubusercontent.com/apache/sling-org-apache-sling-launchpad-contrib-testing/master/README.md
 | grep sling:badge
![sling:badge:contrib](https://img.shields.io/badge/sling-contrib-blue.svg)
{code}
We should consolidate all that and ideally generate all the outputs from a 
single master list that's automatically updated at regular intervals.


was (Author: bdelacretaz):
Trying to summarize the various initiatives going on, as well as our 
requirements, please correct/complete as needed.

*Inputs*
* Either the GitHub API to list all Sling repositories as currently used at 
https://github.com/apache/sling-aggregator
* Or the Gitbox OPML at https://gitbox.apache.org/repos/asf?a=opml as currently 
used by https://github.com/oliverlietz/apache-sling-aggregator

*Desired Outputs*
* 1) A manifest for the Google Repo tool, which requires just the repository 
names and their paths.
* 2) A list suitable for updating http://sling.apache.org/repolist.html (or a 
similar canonical Web page)
* 3) A Maven reactor pom that allows for building everything or sets of 
modules, probably based on Maven profiles

For 1) I haven't checked if the Repo manifest format officially allows us to 
add extra information, currently we have an additional "groups" attribute, if 
that's supported we might add "tags", "badges" and "descriptions" as needed.

For 2) the repositories need to be grouped by functional areas (already 
partially done) and should also have tags or badges for 

[jira] [Commented] (SLING-7262) Generate reusable lists of Git repositories for machine consumption

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-7262:


Trying to summarize the various initiatives going on, as well as our 
requirements, please correct/complete as needed.

*Inputs*
* Either the GitHub API to list all Sling repositories as currently used at 
https://github.com/apache/sling-aggregator
* Or the Gitbox OPML at https://gitbox.apache.org/repos/asf?a=opml as currently 
used by https://github.com/oliverlietz/apache-sling-aggregator

*Desired Outputs*
* 1) A manifest for the Google Repo tool, which requires just the repository 
names and their paths.
* 2) A list suitable for updating http://sling.apache.org/repolist.html (or a 
similar canonical Web page)
* 3) A Maven reactor pom that allows for building everything or sets of 
modules, probably based on Maven profiles

For 1) I haven't checked if the Repo manifest format officially allows us to 
add extra information, currently we have an additional "groups" attribute, if 
that's supported we might add "tags", "badges" and "descriptions" as needed.

For 2) the repositories need to be grouped by functional areas (already 
partially done) and should also have tags or badges for contrib/core/legacy and 
similar classifications. It would be nice to have a brief description of each 
repository as well in that list, maybe the first few lines of their README 
(excluding "belongs to Apache Sling" of course)

*Environment*
The generation of these files needs to run as a Jenkins build so that they can 
be regenerated automatically.

Commiting the output of Jenkins jobs to Git is easy if the target is the 
{{asf-site}} branch, for that we just need to tie the jobs to nodes having the 
{{git-websites}} label. Committing the output to the {{asf-site}} branch of the 
https://github.com/apache/sling-site repository seems to be a good solution to 
me and other scripts can pick it up there at a stable URL, even if the raw 
result is not visible on the website.

*Here's what we currently have "in production"*
* https://github.com/apache/sling-aggregator generates a Repo manifest, needs 
to be updated manually by running a script and pushing the result when new Git 
repos are created
* http://sling.apache.org/repolist.html is generated from that Repo manifest. 
It's missing tags/badges and descriptions
* Our Jenkins jobs are generated from 
https://github.com/apache/sling-tooling-jenkins and optionally use information 
from a {{.sling-module.xml}} file described at 
https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor
* I don't think we have an official Maven aggregator pom at this point
* [~olli] has been working on 
https://github.com/oliverlietz/apache-sling-aggregator with useful things in 
various branches of that repository, which generate a Repo manifest, a Maven 
pom and a GitHub page.

See https://github.com/apache/sling-org-apache-sling-launchpad-contrib-testing 
for an example of a sling:contrib badge that can easily be parsed from the 
README and is displayed there, as opposed to {{.sling-module.xml}} which has no 
impact on the README page on GitHub:

{code}
curl -s 
https://raw.githubusercontent.com/apache/sling-org-apache-sling-launchpad-contrib-testing/master/README.md
 | grep sling:badge
![sling:badge:contrib](https://img.shields.io/badge/sling-contrib-blue.svg)
{code}

We should consolidate all that and ideally generate all the outputs from a 
single master list that's automatically updated at regular intervals.

> Generate reusable lists of Git repositories for machine consumption
> ---
>
> Key: SLING-7262
> URL: https://issues.apache.org/jira/browse/SLING-7262
> Project: Sling
>  Issue Type: Task
>  Components: Build and Source Control
>Reporter: Robert Munteanu
>Priority: Major
>
> We currently have two 'clients' that query the github repos and the 
> .sling-module.xml descriptors:
> * the jenkins job creation DSL script
> * the repo manifest creation script
> We've also discussed in SLING-7161 the possibility of listing all 
> repositories on the website.
> To minimize the effort of talking to github in each location and reduce the 
> number of calls to Github ( for rate limiting purposes ) we should generate a 
> JSON/XML file that contains all information about the git repos. This file is 
> in turns read by various "clients" that need the information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SLING-7262) Generate reusable lists of Git repositories for machine consumption

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated SLING-7262:
---
Summary: Generate reusable lists of Git repositories for machine 
consumption  (was: Generate reusable list of repositories for machine 
consumption)

> Generate reusable lists of Git repositories for machine consumption
> ---
>
> Key: SLING-7262
> URL: https://issues.apache.org/jira/browse/SLING-7262
> Project: Sling
>  Issue Type: Task
>  Components: Build and Source Control
>Reporter: Robert Munteanu
>Priority: Major
>
> We currently have two 'clients' that query the github repos and the 
> .sling-module.xml descriptors:
> * the jenkins job creation DSL script
> * the repo manifest creation script
> We've also discussed in SLING-7161 the possibility of listing all 
> repositories on the website.
> To minimize the effort of talking to github in each location and reduce the 
> number of calls to Github ( for rate limiting purposes ) we should generate a 
> JSON/XML file that contains all information about the git repos. This file is 
> in turns read by various "clients" that need the information.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: apache/sling as github landing repository

[Bertrand Delacretaz]

Hi,

On Wed, Jan 31, 2018 at 9:23 AM, Robert Munteanu  wrote:
> On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote:
>>... 4. add the aggregator and new landing page readme on the master
>> branch, which will be push-able for committers...
>>
> ...The only downside would be that
> cloning the repository would be really slow due to the large size

I think we need to have the aggregator [0] run a regular build to
update the list of Git repositories, soon. That becomes more important
as that list starts including tags, contrib/core/etc status and other
metadata that will change more often than now.

I don't think a large Git repository is a good place for such an
automatically built list of Git repositories metadata, as Jenkins
would need to transfer lots of unneeded data, a dedicated small
repository is much better for that. And I'm not sure right now how to
push the output of that to any branch from builds.apache.org, at this
point I only know how to commit to an asf-site branch (by tying the
Jenkins build to build nodes having the git-websites label).

-Bertrand

> [0] https://github.com/apache/sling-aggregator - which needs a Maven build to 
> be automated

Re: apache/sling as github landing repository

[Robert Munteanu]

On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote:
> On 30.01.2018, at 01:38, Robert Munteanu  wrote:
> > The constraint that we worked with is that many links would be
> > pointing
> > to https://github.com/apache/sling and these would be broken if we
> > added another 'sling' repository to the mix.  So we decided to keep
> > the
> > old 'sling' repository in place, renamed, so links would not break.
> 
> What new links were you thinking of?

Links to commits and files from the old sling repo. For example

* https://github.com/apache/sling/commit/368f5f9c9f6d4c0e2602065687d95e
b173f94b85
* https://github.com/apache/sling/blob/trunk/bundles/extensions/bundler
esource/src/main/java/org/apache/sling/bundleresource/impl/BundleResour
ce.java

These would break if we add another 'sling' repo but work since we
renamed 'sling' to 'sling-old-svn-mirror' and Github is adding
redirects.

That's the main argument against adding a new Git "native" repo as
"sling".

> 
> IIUC, it would be only a README.md and some others markdown files,
> plus the few xml files in sling-aggregator [0] in the "master"
> branch. Which is by design not in the old repo which used subversions
> "trunk".
> 
> Note that any link to a file or subfolder in github would always
> include the branch name.  Not sure if you would ever create branches
> other than "master" for this "landing" repo, and any that would
> conflict with the few fixed branches from the old repo [1].
> 
> tl;dr I don't think there is any chance for conflicts.

Right, but it's not about conflicts, it's about breaking old links.
Backwards compatiblity and all that :-)

> 
> > The Sling SVN repository is read-only to make sure we don't
> > accidentally commit changes there. We would need to go through
> > infra
> > for each change so frequent updates
> 
> Would it be possible to transform the github apache/sling repo, being
> a read-only mirror of the svn one (IIUC), into an active github repo?
> This might be a one time change, but you can still protect the old
> stuff.
> 
> Something like this:
> 1. delete apache/sling-old-svn-mirror on github and disable the
> mirroring (infra team?)
> 2. re-create apache/sling from the git mirror repos available at ASF
> (infra team?)
> 3. make all the old branches protected so they can't be modified
> anymore
> 4. add the aggregator and new landing page readme on the master
> branch, which will be push-able for committers
> 
> wdyt?

Actually that's not a bad idea :-) The only downside would be that
cloning the repository would be really slow due to the large size. Not
sure if we can work around it.

What do others think?

Robert

> 
> [0] https://github.com/apache/sling-aggregator
> [1] https://github.com/apache/sling-old-svn-mirror/branches/all
> 
> Cheers,
> Alex