[jira] [Created] (SLING-5554) Sightly: allow calling data-sly-use with a resource path

2016-02-23 Thread Vlad Bailescu (JIRA) 
Vlad Bailescu created SLING-5554:


 Summary: Sightly: allow calling data-sly-use with a resource path
 Key: SLING-5554
 URL: https://issues.apache.org/jira/browse/SLING-5554
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Affects Versions: Scripting Sightly Engine 1.0.0
Reporter: Vlad Bailescu
Priority: Minor


Following the [discussion on 
dev@sling.apache.org|http://mail-archives.apache.org/mod_mbox/sling-dev/201601.mbox/%3CCANG90TY3xo+kHC=rb30enap7dqgzeymrr4kg1tvzu+s8zw5...@mail.gmail.com%3E]
 I believe it would be nice if we can bind a resource (by path) to a variable 
using {{data-sly-use}}:

{code}
data-sly-use.myResource="${ '/content/myResource' }"
{code}

This will eliminate the need to create an use object for simple cases when we 
are reading properties from other resources.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Resource Resolver 1.4.4

2016-02-23 Thread Daniel Klco 
+1

On Tue, Feb 23, 2016 at 1:43 AM, Carsten Ziegeler 
wrote:

> Hi,
>
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12334879
>
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1428/
>
> 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 1428 /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.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

2016-02-23 Thread Stefan Egli 
+1

Cheers,
Stefan

On 23/02/16 17:10, "Bertrand Delacretaz"  wrote:

>Hi,
>
>We solved 3 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12334310
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1432/
>
>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 1432 /tmp/sling-staging
>
>Note that the Apache Sling Background Servlets Engine 1.0.4 was just
>ready when I was made aware of SLING-5553, so I canceled that release.
>
>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.
>
>Here's my +1
>
>-Bertrand

[jira] [Closed] (SLING-5531) Sling-Namespaces bundle header for registering JCR namespaces broken

2016-02-23 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler closed SLING-5531.
---

> Sling-Namespaces bundle header for registering JCR namespaces broken
> 
>
> Key: SLING-5531
> URL: https://issues.apache.org/jira/browse/SLING-5531
> Project: Sling
>  Issue Type: Bug
>  Components: JCR
>Affects Versions: JCR Base 2.3.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Critical
> Fix For: JCR Base 2.3.2
>
> Attachments: AbstractSlingRepository2.patch
>
>
> the changes for SLING-4937 (Drop namespace mapping support) broke the 
> "Declared Node Type Registration" feature described in [1].
> this allows to register custom JCR namespaces or nodetypes via a CND file 
> when deploying a bundle and specifying the CND file via a {{Sling-Nodetypes}} 
> bundle header.
> i assume only the support for {{Sling-Namespaces}} should be removed with 
> SLING-4937, not the support for {{Sling-Nodetypes}}.
> [1] 
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Scripting Sightly Engine 1.0.14

2016-02-23 Thread Carsten Ziegeler 
+1


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

[VOTE RESULT] Release Apache Sling JCR Base 2.3.2

2016-02-23 Thread Carsten Ziegeler 
THe vote passed with three binding +1 votes

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

Re: [VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

2016-02-23 Thread Carsten Ziegeler 
+1


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

Re: [VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

2016-02-23 Thread Daniel Klco 
+1

On Tue, Feb 23, 2016 at 11:10 AM, Bertrand Delacretaz <
bdelacre...@apache.org> wrote:

> Hi,
>
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12334310
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1432/
>
> 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 1432 /tmp/sling-staging
>
> Note that the Apache Sling Background Servlets Engine 1.0.4 was just
> ready when I was made aware of SLING-5553, so I canceled that release.
>
> 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.
>
> Here's my +1
>
> -Bertrand
>

Re: [VOTE] Release Apache Sling Scripting Sightly Engine 1.0.14

2016-02-23 Thread Daniel Klco 
+1

On Tue, Feb 23, 2016 at 11:08 AM, Stefan Seifert 
wrote:

> +1
>

RE: [VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

2016-02-23 Thread Stefan Seifert 
+1

[jira] [Closed] (SLING-4119) ResourceResolver unable to map SSL-forwarded request

2016-02-23 Thread Carsten Ziegeler (JIRA) 

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

Carsten Ziegeler closed SLING-4119.
---

> ResourceResolver unable to map SSL-forwarded request
> 
>
> Key: SLING-4119
> URL: https://issues.apache.org/jira/browse/SLING-4119
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.0.6
>Reporter: Dominique Pfister
> Fix For: Resource Resolver 1.0.6
>
>
> I've setup two hosts in my /etc/map as follows:
> {code}
> /etc/map
> +--http
> +--example1.com
> +--sling:internalRedirect = ["/content/example1","/"]
> +--example1_com
> +--sling:internalRedirect = ["/content/example1/index.html"]
> +--sling:match = "example1.com/$"
> +--example2.com
> +--sling:internalRedirect = ["/content/example2","/"]
> +--example2_com
> +--sling:internalRedirect = ["/content/example2/index.html"]
> +--sling:match = "example2.com/$"
> {code}
> I have a reverse proxy in front of Sling, listening on port 80, that will 
> forward incoming requests with the original "Host" header. If incoming 
> requests are over plain HTTP (e.g. to http://example1.com)  everything works 
> as expected, I get 200 status code from Sling as internal redirects are made 
> to the respective home pages of the hosts.
> However, if I start a second, secure listener on port 443, forwarding 
> incoming requests to Sling over HTTP (bearing a header "X-Forwarded-SSL: 
> on"), the resource resolver will start to issue 302 redirects, as it is 
> unable to find some match. 
> E.g., a request for "https://example1.com;, arrives at Sling as follows:
> {code}
> GET / HTTP/1.1
> Host: example1.com
> X-Forwarded-SSL: on
> ...
> {code}
> The resource resolver logs this as:
> {code}
> Resolving request path: https/example1.com.80/
> {code}
> Note that the scheme change is due to Apache Felix's SSL Filter, overriding 
> {{ServletRequest.getScheme}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5553) Start background servlet jobs for POST, PUT and DELETE only by default

2016-02-23 Thread Bertrand Delacretaz (JIRA) 

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

Bertrand Delacretaz resolved SLING-5553.

Resolution: Fixed

Implemented in http://svn.apache.org/r1731890

> Start background servlet jobs for POST, PUT and DELETE only by default
> --
>
> Key: SLING-5553
> URL: https://issues.apache.org/jira/browse/SLING-5553
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Background Servlets 1.0.2
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Background Servlets 1.0.6
>
>
> Starting background jobs does not make sense for GET and HEAD requests for 
> example, as those jobs are meant to change content and that shouldn't happen 
> for such requests. I'll add a configurable list of acceptable methods to the 
> {{BackgroundServletStarterFilter}}, defaulting to POST, PUT and DELETE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] Release Apache Sling Background Servlets Engine 1.0.6 and Background Servlets Integration Tests 1.0.0

2016-02-23 Thread Bertrand Delacretaz 
Hi,

We solved 3 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12334310

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

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 1432 /tmp/sling-staging

Note that the Apache Sling Background Servlets Engine 1.0.4 was just
ready when I was made aware of SLING-5553, so I canceled that release.

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.

Here's my +1

-Bertrand

RE: [VOTE] Release Apache Sling Scripting Sightly Engine 1.0.14

2016-02-23 Thread Stefan Seifert 
+1

Re: [VOTE] Release Apache Sling Scripting Sightly Engine 1.0.14

2016-02-23 Thread Stefan Egli 
+1

Cheers,
Stefan

On 23/02/16 16:06, "Radu Cotescu"  wrote:

>Hi,
>
>We solved 1 issue in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12334765
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1431
>
>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 1431 /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.
>
>Thanks,
>Radu

[jira] [Created] (SLING-5553) Start background servlet jobs for POST, PUT and DELETE only by default

2016-02-23 Thread Bertrand Delacretaz (JIRA) 
Bertrand Delacretaz created SLING-5553:
--

 Summary: Start background servlet jobs for POST, PUT and DELETE 
only by default
 Key: SLING-5553
 URL: https://issues.apache.org/jira/browse/SLING-5553
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Background Servlets 1.0.2
Reporter: Bertrand Delacretaz
Assignee: Bertrand Delacretaz
Priority: Minor
 Fix For: Background Servlets 1.0.4


Starting background jobs does not make sense for GET and HEAD requests for 
example, as those jobs are meant to change content and that shouldn't happen 
for such requests. I'll add a configurable list of acceptable methods to the 
{{BackgroundServletStarterFilter}}, defaulting to POST, PUT and DELETE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5551) MockSlingHttpServletRequest: make sure given bundleContext is used

2016-02-23 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert resolved SLING-5551.
---
Resolution: Fixed

sling-mock 1.x: rev. 1731881  
sling-mock 2.x: rev. 1731765

> MockSlingHttpServletRequest: make sure given bundleContext is used
> --
>
> Key: SLING-5551
> URL: https://issues.apache.org/jira/browse/SLING-5551
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: Testing Sling Mock 1.6.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Trivial
>  Labels: mocks
> Fix For: Testing Sling Mock 1.6.4, Testing Sling Mock 2.0.0
>
>
> when using the {{MockSlingHttpServletRequest(BundleContext bundleContext)}} 
> constructor within sling-mock the bundle context is not correctly store in 
> the member field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5552) ModelAdapterFactoryUtil: Suppress info log messages from Reflections library

2016-02-23 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert resolved SLING-5552.
---
Resolution: Fixed

sling-mock 1.x: rev. 1731883  
sling-mock 2.x: rev. 1731771

> ModelAdapterFactoryUtil: Suppress info log messages from Reflections library
> 
>
> Key: SLING-5552
> URL: https://issues.apache.org/jira/browse/SLING-5552
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Testing Sling Mock 1.6.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Trivial
>  Labels: mocks
> Fix For: Testing Sling Mock 1.6.4, Testing Sling Mock 2.0.0
>
>
> when registering sling models in unit tests a lot of messages in INFO level 
> are generated by the "Relfections" library used internally. this is not 
> required and should be suppressed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-5552) ModelAdapterFactoryUtil: Suppress info log messages from Reflections library

2016-02-23 Thread Stefan Seifert (JIRA) 
Stefan Seifert created SLING-5552:
-

 Summary: ModelAdapterFactoryUtil: Suppress info log messages from 
Reflections library
 Key: SLING-5552
 URL: https://issues.apache.org/jira/browse/SLING-5552
 Project: Sling
  Issue Type: Improvement
  Components: Testing
Affects Versions: Testing Sling Mock 1.6.2
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Trivial
 Fix For: Testing Sling Mock 1.6.4, Testing Sling Mock 2.0.0


when registering sling models in unit tests a lot of messages in INFO level are 
generated by the "Relfections" library used internally. this is not required 
and should be suppressed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] Release Apache Sling Scripting Sightly Engine 1.0.14

2016-02-23 Thread Radu Cotescu 
Hi,

We solved 1 issue in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12334765

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

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 1431 /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.

Thanks,
Radu

[jira] [Created] (SLING-5551) MockSlingHttpServletRequest: make sure given bundleContext is used

2016-02-23 Thread Stefan Seifert (JIRA) 
Stefan Seifert created SLING-5551:
-

 Summary: MockSlingHttpServletRequest: make sure given 
bundleContext is used
 Key: SLING-5551
 URL: https://issues.apache.org/jira/browse/SLING-5551
 Project: Sling
  Issue Type: Bug
  Components: Testing
Affects Versions: Testing Sling Mock 1.6.2
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Trivial
 Fix For: Testing Sling Mock 1.6.4, Testing Sling Mock 2.0.0


when using the {{MockSlingHttpServletRequest(BundleContext bundleContext)}} 
constructor within sling-mock the bundle context is not correctly store in the 
member field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (SLING-5543) Sightly Use POJOs with CR+LF line endings are not compiled correctly

2016-02-23 Thread Radu Cotescu (JIRA) 

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

Radu Cotescu edited comment on SLING-5543 at 2/23/16 2:58 PM:
--

Fixed in 
[r1731860|https://svn.apache.org/viewvc?view=revision=1731860] and 
[r1731873|https://svn.apache.org/viewvc?view=revision=r1731873].


was (Author: radu.cotescu):
Fixed in 
[r1731860|https://svn.apache.org/viewvc?view=revision=1731860].

> Sightly Use POJOs with CR+LF line endings are not compiled correctly
> 
>
> Key: SLING-5543
> URL: https://issues.apache.org/jira/browse/SLING-5543
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.10, Scripting Sightly 
> Engine 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.14
>
>
> If a Sightly Use POJO has {{CR+LF}} line endings then the 
> {{SightlyJavaCompilerService}} will fail to correctly compile it due to 
> issues with the {{package}} declaration, which is now handled automatically 
> by the compiler - SLING-5409.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-5543) Sightly Use POJOs with CR+LF line endings are not compiled correctly

2016-02-23 Thread Radu Cotescu (JIRA) 

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

Radu Cotescu resolved SLING-5543.
-
Resolution: Fixed

Fixed in 
[r1731860|https://svn.apache.org/viewvc?view=revision=1731860].

> Sightly Use POJOs with CR+LF line endings are not compiled correctly
> 
>
> Key: SLING-5543
> URL: https://issues.apache.org/jira/browse/SLING-5543
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Sightly Engine 1.0.10, Scripting Sightly 
> Engine 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.14
>
>
> If a Sightly Use POJO has {{CR+LF}} line endings then the 
> {{SightlyJavaCompilerService}} will fail to correctly compile it due to 
> issues with the {{package}} declaration, which is now handled automatically 
> by the compiler - SLING-5409.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

adaptTo() 2016 conference

2016-02-23 Thread Stefan Seifert 
Hi everyone,

with the good memories of last year's adaptTo() still in mind, we are beginning 
to set our focus on this year's convention.

adaptTo() is a conference focused on Apache Sling, including Apache Felix and 
Apache Jackrabbit. If you are not familiar with our event yet, you might find 
something interesting in the sessions from last year 
(http://adapt.to/2015/en/schedule.html).

adaptTo() 2016 will again take place in the Kulturbrauerei, Berlin, 26th-28th 
of September (Mon-Wed).

So what's new? We are offering an early bird ticket this year. 
There will be a discount of over 20% on tickets bought before 30th April.
Registration is now open: http://adapt.to/tickets.

There is a special discount for Apache Committers, see 
http://adapt.to/conference for details.

Also, for the first time, the event is open for sponsors. Sponsor packages are 
listed at http://adapt.to/sponsors.

Most importantly, however, we are excited and curious about the new topics and 
projects you want to talk about. 
Our call for papers is open from today until 22th of April.
Of course, everyone is welcome to contribute. For more information see 
http://adapt.to/cfp.

Visit us at http://adapt.to or share your thoughts via i...@adaptto.org or 
#adaptTo.

Have a great weekend and we look forward to hearing from you soon.

Kind regards on behalf of the adaptTo() Team,
Stefan Seifert

[jira] [Resolved] (SLING-5550) Optimize acquire package operation to make fewer saves

2016-02-23 Thread Marius Petria (JIRA) 

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

Marius Petria resolved SLING-5550.
--
Resolution: Fixed

Committed revision 1731829.


> Optimize acquire package operation to make fewer saves
> --
>
> Key: SLING-5550
> URL: https://issues.apache.org/jira/browse/SLING-5550
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Marius Petria
>
> Currently the SharedDistributionPackage.acquire is called for each queue and 
> a save into the repo is done each time. We can send an array of queues for 
> which the package should be acquired and do just one save for all queues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Resource Resolver 1.4.4

2016-02-23 Thread Antonio Sanso 
+1
On Feb 23, 2016, at 7:43 AM, Carsten Ziegeler  wrote:

> Hi,
> 
> We solved 3 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12334879
> 
> 
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1428/
> 
> 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 1428 /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.
> 
> Regards
> Carsten
> -- 
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

RE: [VOTE] Release Apache Sling Resource Resolver 1.4.4

2016-02-23 Thread Stefan Seifert 
+1

[jira] [Updated] (SLING-5545) Potential NPE in ResourceProviderTracker.postEvents during shutdown

2016-02-23 Thread Stefan Seifert (JIRA) 

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

Stefan Seifert updated SLING-5545:
--
Description: 
the method ResourceProviderTracker.postEvents, line 410 may throw an event if 
an event is posted while the service is already shutting down (listener is 
already null in this case).

listener method should only be called if listener object is not null.

  was:
the method ResourceProviderTracker.postEvents, line 410 may throw an event if 
and event is posted while the service is already shutting down (listener is 
already null in this case).

listener method should only called if listener object is not null.


> Potential NPE in ResourceProviderTracker.postEvents during shutdown
> ---
>
> Key: SLING-5545
> URL: https://issues.apache.org/jira/browse/SLING-5545
> Project: Sling
>  Issue Type: Bug
>  Components: ResourceResolver
>Affects Versions: Resource Resolver 1.4.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Resource Resolver 1.4.4
>
>
> the method ResourceProviderTracker.postEvents, line 410 may throw an event if 
> an event is posted while the service is already shutting down (listener is 
> already null in this case).
> listener method should only be called if listener object is not null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling Resource Resolver 1.4.4

2016-02-23 Thread Stefan Egli 
+1

Cheers,
Stefan

On 23/02/16 07:43, "Carsten Ziegeler"  wrote:

>Hi,
>
>We solved 3 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12334879
>
>
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1428/
>
>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 1428 /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.
>
>Regards
>Carsten
>-- 
>Carsten Ziegeler
>Adobe Research Switzerland
>cziege...@apache.org

[jira] [Created] (SLING-5550) Optimize acquire package operation to make fewer saves

2016-02-23 Thread Marius Petria (JIRA) 
Marius Petria created SLING-5550:


 Summary: Optimize acquire package operation to make fewer saves
 Key: SLING-5550
 URL: https://issues.apache.org/jira/browse/SLING-5550
 Project: Sling
  Issue Type: Improvement
  Components: Distribution
Reporter: Marius Petria


Currently the SharedDistributionPackage.acquire is called for each queue and a 
save into the repo is done each time. We can send an array of queues for which 
the package should be acquired and do just one save for all queues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)