[Jenkins] Sling » sling-org-apache-sling-launchpad-testing » master #575 is BROKEN

2020-02-08 Thread Apache Jenkins Server
Please see 
https://builds.apache.org/job/Sling/job/sling-org-apache-sling-launchpad-testing/job/master/575/
 for details.

No further emails will be sent until the status of the build is changed.
Build log follows below:

[...truncated 3120 lines...]
at 
org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
at org.apache.felix.framework.Felix.access$000(Felix.java:112)
at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:434)
at 
org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:170)
at 
org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:145)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager$3.unregister(AbstractComponentManager.java:927)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager$3.unregister(AbstractComponentManager.java:892)
at 
org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:135)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.unregisterService(AbstractComponentManager.java:969)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.doDeactivate(AbstractComponentManager.java:823)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.deactivateInternal(AbstractComponentManager.java:805)
at 
org.apache.felix.scr.impl.manager.AbstractComponentManager.dispose(AbstractComponentManager.java:584)
at 
org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.disposeComponents(ConfigurableComponentHolder.java:716)
at 
org.apache.felix.scr.impl.BundleComponentActivator.dispose(BundleComponentActivator.java:510)
at 
org.apache.felix.scr.impl.Activator.disposeComponents(Activator.java:429)
at org.apache.felix.scr.impl.Activator.access$300(Activator.java:49)
at 
org.apache.felix.scr.impl.Activator$ScrExtension.destroy(Activator.java:292)
at 
org.apache.felix.scr.impl.AbstractExtender$1.run(AbstractExtender.java:216)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
org.apache.felix.scr.impl.AbstractExtender.destroyExtension(AbstractExtender.java:238)
at 
org.apache.felix.scr.impl.AbstractExtender.bundleChanged(AbstractExtender.java:132)
at 
org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915)
at 
org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)
at 
org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4817)
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2785)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1557)
at 
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.base/java.lang.Thread.run(Thread.java:830)
Warning: Nashorn engine is planned to be removed from a future JDK release
[DEBUG] [ServiceReference 149 from bundle 60 : 
org.apache.sling.launchpad.test-services:12.0.0.SNAPSHOT 
ref=[javax.servlet.Servlet] properties={component.id=52, 
component.name=org.apache.sling.launchpad.testservices.servlets.R6WhiteboardServlet,
 objectClass=[javax.servlet.Servlet], 
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=org.apache.sling),
 osgi.http.whiteboard.servlet.pattern=/whiteboard_r6, service.bundleid=60, 
service.id=149, 
service.pid=org.apache.sling.launchpad.testservices.servlets.R6WhiteboardServlet,
 service.scope=bundle, service.vendor=The Apache Software Foundation}] Ignoring 
unmatching Servlet service
[DEBUG] [ServiceReference 357 from bundle 144 : org.apache.sling.engine:2.6.22 
ref=[javax.servlet.Servlet] properties={component.id=250, 
component.name=org.apache.sling.engine.impl.SlingMainServlet, 
objectClass=[javax.servlet.Servlet], 
osgi.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=org.apache.sling),
 osgi.http.whiteboard.servlet.pattern=/, service.bundleid=144, 
service.description=Apache Sling Engine Main Servlet, service.id=357, 
service.scope=singleton, service.vendor=The Apache Software Foundation, 
servlet-name=ApacheSling/2.6, 
sling.additional.response.headers=[Ljava.lang.String;@5ba61532, 
sling.max.calls=1000, sling.max.inclusions=50, sling.max.record.requests=20, 
sling.trace.allow=false}] Ignoring unmatching Servlet service
[DEBUG] [ServiceReference 375 from bundle 144 : org.apache.sling.engine:2.6.22 
ref=[javax.servlet.Filter] properties={component.id=255, 
component.name=org.apache.sling.engine.parameters, file.max=-1, 
file.threshold=256000, 

[jira] [Resolved] (SLING-8917) CMS - Add Support for LDAP

2020-02-08 Thread Dan Klco (Jira)


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

Dan Klco resolved SLING-8917.
-
Resolution: Fixed

Fixed in 
[https://github.com/apache/sling-org-apache-sling-app-cms/commit/d913ef8c7515c1851c4a4be2e5072f374447d531]

> CMS - Add Support for LDAP
> --
>
> Key: SLING-8917
> URL: https://issues.apache.org/jira/browse/SLING-8917
> Project: Sling
>  Issue Type: Improvement
>  Components: App CMS
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Minor
>  Labels: backlog
>
> Look into adding LDAP support via OAK LDAP: 
> [https://jackrabbit.apache.org/oak/docs/security/authentication/ldap.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (SLING-8917) CMS - Add Support for LDAP

2020-02-08 Thread Dan Klco (Jira)


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

Dan Klco updated SLING-8917:

Fix Version/s: CMS 0.14.2

> CMS - Add Support for LDAP
> --
>
> Key: SLING-8917
> URL: https://issues.apache.org/jira/browse/SLING-8917
> Project: Sling
>  Issue Type: Improvement
>  Components: App CMS
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Minor
>  Labels: backlog
> Fix For: CMS 0.14.2
>
>
> Look into adding LDAP support via OAK LDAP: 
> [https://jackrabbit.apache.org/oak/docs/security/authentication/ldap.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Redirect Provider

2020-02-08 Thread Robert Munteanu
Hi Ian,

On Sat, 2020-02-08 at 09:48 +, Ian Boston wrote:
> Hi,
> The PRs have been opened, see the issue.
> I will do complete implementations to verify it works as required in
> AEM.
> I would also like to insure no disruption to Sling, and since it's
> been a
> long time since I did this, how do run full CI/CD and integrate a new
> API
> in Sling ? (a pointer would be great).
> 

I have added some instructions at 

  https://sling.apache.org/contributing.html#testing

Let me know whether that is enough or it needs expansions.

Thanks,
Robert

> Best Regards
> Ian
> 
> 
> On Sat, 8 Feb 2020 at 09:23, Ian Boston  wrote:
> 
> > Hi,
> > Opened [1] to track the work.
> > Best Regards
> > Ian
> > 
> > 1 https://issues.apache.org/jira/browse/SLING-9060
> > 
> > On Wed, 5 Feb 2020 at 22:12, Ian Boston  wrote:
> > 
> > > Hi,
> > > Ok.
> > > 
> > > o.a.s.api.redirect for the API, and a patch to the Get servlet to
> > > use the
> > > API.
> > > Will do PRs shortly.
> > > 
> > > Best Regards
> > > Ian
> > > 
> > > 
> > > On Tue, 4 Feb 2020 at 14:13, Bertrand Delacretaz <
> > > bdelacre...@apache.org>
> > > wrote:
> > > 
> > > > On Tue, Feb 4, 2020 at 1:58 PM Ian Boston 
> > > > wrote:
> > > > > ...New package, agreed, no ripples.
> > > > > o.a.s.api.response ? ...
> > > > 
> > > > o.a.s.api.redirect is more specific and I think having packages
> > > > with
> > > > few interfaces is fine?
> > > > 
> > > > The existing api.auth and api.security packages for example
> > > > only have
> > > > 3 items each.
> > > > 
> > > > It has the benefit of OSGi package versioning being very
> > > > specific.
> > > > 
> > > > -Bertrand
> > > > 



Re: Redirect Provider

2020-02-08 Thread Ian Boston
Hi,
The PRs have been opened, see the issue.
I will do complete implementations to verify it works as required in AEM.
I would also like to insure no disruption to Sling, and since it's been a
long time since I did this, how do run full CI/CD and integrate a new API
in Sling ? (a pointer would be great).
Best Regards
Ian


On Sat, 8 Feb 2020 at 09:23, Ian Boston  wrote:

> Hi,
> Opened [1] to track the work.
> Best Regards
> Ian
>
> 1 https://issues.apache.org/jira/browse/SLING-9060
>
> On Wed, 5 Feb 2020 at 22:12, Ian Boston  wrote:
>
>> Hi,
>> Ok.
>>
>> o.a.s.api.redirect for the API, and a patch to the Get servlet to use the
>> API.
>> Will do PRs shortly.
>>
>> Best Regards
>> Ian
>>
>>
>> On Tue, 4 Feb 2020 at 14:13, Bertrand Delacretaz 
>> wrote:
>>
>>> On Tue, Feb 4, 2020 at 1:58 PM Ian Boston  wrote:
>>> > ...New package, agreed, no ripples.
>>> > o.a.s.api.response ? ...
>>>
>>> o.a.s.api.redirect is more specific and I think having packages with
>>> few interfaces is fine?
>>>
>>> The existing api.auth and api.security packages for example only have
>>> 3 items each.
>>>
>>> It has the benefit of OSGi package versioning being very specific.
>>>
>>> -Bertrand
>>>
>>


[jira] [Commented] (SLING-9060) Improve Redirect handling for Resources that can be served from alternative URLs

2020-02-08 Thread Ian Boston (Jira)


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

Ian Boston commented on SLING-9060:
---

PRs 

https://github.com/apache/sling-org-apache-sling-api/pull/17

[https://github.com/apache/sling-org-apache-sling-servlets-get/pull/4]

 

> Improve Redirect handling for Resources that can be served from alternative 
> URLs
> 
>
> Key: SLING-9060
> URL: https://issues.apache.org/jira/browse/SLING-9060
> Project: Sling
>  Issue Type: Improvement
>  Components: API, Servlets
>Affects Versions: API 2.22.0, Servlets Get 2.1.40
>Reporter: Ian Boston
>Assignee: Ian Boston
>Priority: Major
> Fix For: Servlets Get 2.1.42, API 2.23.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Improve the mechanism used to redirect streamed binary requests so that it 
> has the context of the request and can be extended without provider API 
> changes.
>  
> This was discussed on list at [https://markmail.org/message/msmxgulkmzx7czth 
> |https://markmail.org/message/msmxgulkmzx7czth]
> PR to follow



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (SLING-9060) Improve Redirect handling for Resources that can be served from alternative URLs

2020-02-08 Thread Ian Boston (Jira)


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

Ian Boston reassigned SLING-9060:
-

Assignee: Ian Boston

> Improve Redirect handling for Resources that can be served from alternative 
> URLs
> 
>
> Key: SLING-9060
> URL: https://issues.apache.org/jira/browse/SLING-9060
> Project: Sling
>  Issue Type: Improvement
>  Components: API, Servlets
>Affects Versions: API 2.22.0, Servlets Get 2.1.40
>Reporter: Ian Boston
>Assignee: Ian Boston
>Priority: Major
> Fix For: Servlets Get 2.1.42, API 2.23.0
>
>
> Improve the mechanism used to redirect streamed binary requests so that it 
> has the context of the request and can be extended without provider API 
> changes.
>  
> This was discussed on list at [https://markmail.org/message/msmxgulkmzx7czth 
> |https://markmail.org/message/msmxgulkmzx7czth]
> PR to follow



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


Re: Redirect Provider

2020-02-08 Thread Ian Boston
Hi,
Opened [1] to track the work.
Best Regards
Ian

1 https://issues.apache.org/jira/browse/SLING-9060

On Wed, 5 Feb 2020 at 22:12, Ian Boston  wrote:

> Hi,
> Ok.
>
> o.a.s.api.redirect for the API, and a patch to the Get servlet to use the
> API.
> Will do PRs shortly.
>
> Best Regards
> Ian
>
>
> On Tue, 4 Feb 2020 at 14:13, Bertrand Delacretaz 
> wrote:
>
>> On Tue, Feb 4, 2020 at 1:58 PM Ian Boston  wrote:
>> > ...New package, agreed, no ripples.
>> > o.a.s.api.response ? ...
>>
>> o.a.s.api.redirect is more specific and I think having packages with
>> few interfaces is fine?
>>
>> The existing api.auth and api.security packages for example only have
>> 3 items each.
>>
>> It has the benefit of OSGi package versioning being very specific.
>>
>> -Bertrand
>>
>


[jira] [Created] (SLING-9060) Improve Redirect handling for Resources that can be served from alternative URLs

2020-02-08 Thread Ian Boston (Jira)
Ian Boston created SLING-9060:
-

 Summary: Improve Redirect handling for Resources that can be 
served from alternative URLs
 Key: SLING-9060
 URL: https://issues.apache.org/jira/browse/SLING-9060
 Project: Sling
  Issue Type: Improvement
  Components: API, Servlets
Affects Versions: Servlets Get 2.1.40, API 2.22.0
Reporter: Ian Boston
 Fix For: API 2.23.0, Servlets Get 2.1.42


Improve the mechanism used to redirect streamed binary requests so that it has 
the context of the request and can be extended without provider API changes.

 

This was discussed on list at [https://markmail.org/message/msmxgulkmzx7czth 
|https://markmail.org/message/msmxgulkmzx7czth]

PR to follow



--
This message was sent by Atlassian Jira
(v8.3.4#803005)