[jira] [Updated] (SLING-5235) Remove loginAdministrative() usage from org.apache.sling.resourceresolver

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-5235:

Fix Version/s: (was: Resource Resolver 1.5.0)
   Resource Resolver 1.5.2

> Remove loginAdministrative() usage from org.apache.sling.resourceresolver
> -
>
> Key: SLING-5235
> URL: https://issues.apache.org/jira/browse/SLING-5235
> Project: Sling
>  Issue Type: Improvement
>  Components: ResourceResolver
>Reporter: Antonio Sanso
> Fix For: Resource Resolver 1.5.2
>
>
> counted 6 occurrences



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

[jira] [Commented] (SLING-6066) Clarify and complete removal resource events

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-6066:
-

Updated javadocs to clarify that this is the task of the resource providers. a 
provider must take care to send all relevant events to the listener.
There is no need to do anything additional in the resource resolver 
implementation as we don't need to send these removal events across providers: 
for example if a provider is mounted at / and another at /a/b . A removal of /a 
in the root RP has no effect on resources of the provider mounted at /a/b

> Clarify and complete removal resource events
> 
>
> Key: SLING-6066
> URL: https://issues.apache.org/jira/browse/SLING-6066
> Project: Sling
>  Issue Type: Improvement
>  Components: API, ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: API 2.15.0, Resource Resolver 1.5.0
>
>
> As recently discussed in the mailing list, if a ResourceChangeListener is 
> interested in removal events, the listener might not get the event it is 
> interested in. For example, if the listener is registered with a glob 
> pattern, like **.jsp, but the parent (or any parent) of a jsp is removed. In 
> that case no removal event for the jsp itself is sent.  Which means the 
> listener is unaware of removals.
> We need to clarify this in the javadocs, but also should implement handling 
> removal in the following:
> If a listener is registered for removal events - regardless if a glob pattern 
> is used or not - the listener will be notified of removals of any parent node 
> up to the top level node. For example if a listener is interested in 
> /a/b/c/**/*.jsp, a removal of any resource below "c", but also removal of 
> "a", "b", or "c" is reported to the listener.



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

[jira] [Resolved] (SLING-6066) Clarify and complete removal resource events

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-6066.
-
Resolution: Fixed

> Clarify and complete removal resource events
> 
>
> Key: SLING-6066
> URL: https://issues.apache.org/jira/browse/SLING-6066
> Project: Sling
>  Issue Type: Improvement
>  Components: API, ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: API 2.15.0, Resource Resolver 1.5.0
>
>
> As recently discussed in the mailing list, if a ResourceChangeListener is 
> interested in removal events, the listener might not get the event it is 
> interested in. For example, if the listener is registered with a glob 
> pattern, like **.jsp, but the parent (or any parent) of a jsp is removed. In 
> that case no removal event for the jsp itself is sent.  Which means the 
> listener is unaware of removals.
> We need to clarify this in the javadocs, but also should implement handling 
> removal in the following:
> If a listener is registered for removal events - regardless if a glob pattern 
> is used or not - the listener will be notified of removals of any parent node 
> up to the top level node. For example if a listener is interested in 
> /a/b/c/**/*.jsp, a removal of any resource below "c", but also removal of 
> "a", "b", or "c" is reported to the listener.



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

[jira] [Updated] (SLING-6066) Clarify and complete removal resource events

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-6066:

Fix Version/s: (was: JCR Resource 2.9.0)

> Clarify and complete removal resource events
> 
>
> Key: SLING-6066
> URL: https://issues.apache.org/jira/browse/SLING-6066
> Project: Sling
>  Issue Type: Improvement
>  Components: API, ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: API 2.15.0, Resource Resolver 1.5.0
>
>
> As recently discussed in the mailing list, if a ResourceChangeListener is 
> interested in removal events, the listener might not get the event it is 
> interested in. For example, if the listener is registered with a glob 
> pattern, like **.jsp, but the parent (or any parent) of a jsp is removed. In 
> that case no removal event for the jsp itself is sent.  Which means the 
> listener is unaware of removals.
> We need to clarify this in the javadocs, but also should implement handling 
> removal in the following:
> If a listener is registered for removal events - regardless if a glob pattern 
> is used or not - the listener will be notified of removals of any parent node 
> up to the top level node. For example if a listener is interested in 
> /a/b/c/**/*.jsp, a removal of any resource below "c", but also removal of 
> "a", "b", or "c" is reported to the listener.



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

[jira] [Updated] (SLING-6066) Clarify and complete removal resource events

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-6066:

Component/s: (was: JCR)

> Clarify and complete removal resource events
> 
>
> Key: SLING-6066
> URL: https://issues.apache.org/jira/browse/SLING-6066
> Project: Sling
>  Issue Type: Improvement
>  Components: API, ResourceResolver
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Blocker
> Fix For: API 2.15.0, Resource Resolver 1.5.0
>
>
> As recently discussed in the mailing list, if a ResourceChangeListener is 
> interested in removal events, the listener might not get the event it is 
> interested in. For example, if the listener is registered with a glob 
> pattern, like **.jsp, but the parent (or any parent) of a jsp is removed. In 
> that case no removal event for the jsp itself is sent.  Which means the 
> listener is unaware of removals.
> We need to clarify this in the javadocs, but also should implement handling 
> removal in the following:
> If a listener is registered for removal events - regardless if a glob pattern 
> is used or not - the listener will be notified of removals of any parent node 
> up to the top level node. For example if a listener is interested in 
> /a/b/c/**/*.jsp, a removal of any resource below "c", but also removal of 
> "a", "b", or "c" is reported to the listener.



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

[jira] [Updated] (SLING-6102) Adding formatter to HTL/Sightly dates

[Feike Visser (JIRA)]

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

Feike Visser updated SLING-6102:

Description: 
When using Sightly we are missing functionality to format dates.

Proposed solution:
{code}
@ dateFormat = ''
{code}

format used can be found in : 
http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html

The value to be formatted must be specified via a Date-type (Date,Calendar etc)

Example
{code}


  ${ dateV @ dateFormat='dd/MM/'}
  ${ obj.jsdate @ dateFormat='dd/MM/'}
  ${ properties.jcr:created  @ dateFormat='dd/MM/' }

  ${ obj.jsdate @ dateFormat='dd/MMM/', locale='ko_KR' } // korean locale
  ${ obj.jsdate @ dateFormat='dd/MMM/', locale='fr_FR' } // french locale
  ${ obj.jsdate @ dateFormat='dd/MMM/' } // locale from request
  ${ obj.jsdate @ dateFormat='dd/MMM/ HH', locale='fr_FR', timezone='PST' } 
// french locale, timezone set to PST
  ${ obj.jsdate @ dateFormat='dd/MMM/ HH', timezone='CTT' } // timezone set 
to CTT


{code}


  was:
When using Sightly we are missing functionality to format dates.

Proposed solution:
{code}
@ dateFormat = ''
{code}

format used can be found in : 
http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html

The value to be formatted must be specified via a Date-type (Date,Calendar etc)

Example
{code}


  ${ dateV @ dateFormat='dd/MM/'}
  ${ obj.jsdate @ dateFormat='dd/MM/'}
  ${ properties.jcr:created  @ dateFormat='dd/MM/' }

  ${ obj.jsdate @ dateFormat='dd/MMM/', locale='ko_KR' } // korean locale
   ${ obj.jsdate @ dateFormat='dd/MMM/', locale='fr_FR' } // french locale
   ${ obj.jsdate @ dateFormat='dd/MMM/' } // locale from request


{code}



> Adding formatter to HTL/Sightly dates
> -
>
> Key: SLING-6102
> URL: https://issues.apache.org/jira/browse/SLING-6102
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Feike Visser
>
> When using Sightly we are missing functionality to format dates.
> Proposed solution:
> {code}
> @ dateFormat = ''
> {code}
> format used can be found in : 
> http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html
> The value to be formatted must be specified via a Date-type (Date,Calendar 
> etc)
> Example
> {code}
> 
>   ${ dateV @ dateFormat='dd/MM/'}
>   ${ obj.jsdate @ dateFormat='dd/MM/'}
>   ${ properties.jcr:created  @ dateFormat='dd/MM/' }
>   ${ obj.jsdate @ dateFormat='dd/MMM/', locale='ko_KR' } // korean locale
>   ${ obj.jsdate @ dateFormat='dd/MMM/', locale='fr_FR' } // french locale
>   ${ obj.jsdate @ dateFormat='dd/MMM/' } // locale from request
>   ${ obj.jsdate @ dateFormat='dd/MMM/ HH', locale='fr_FR', timezone='PST' 
> } // french locale, timezone set to PST
>   ${ obj.jsdate @ dateFormat='dd/MMM/ HH', timezone='CTT' } // timezone 
> set to CTT
> 
> {code}



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

Re: [VOTE] Release Apache Sling Scheduler Support 2.5.2

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 12:15 PM, Carsten Ziegeler 
wrote:

> +1
>
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

[jira] [Comment Edited] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies

[Radu Cotescu (JIRA)]

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

Radu Cotescu edited comment on SLING-6165 at 10/20/16 5:33 PM:
---

--I think we can safely remove those two bundles as I've switched both of them 
to using a service user (SLING-5236).--

Correction, it seems that 
{{org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager#setup}} 
uses {{loginAdministrative}} on behalf of every bundle logging in with a 
service user.


was (Author: radu.cotescu):
I think we can safely remove those two bundles as I've switched both of them to 
using a service user (SLING-5236).

> Expose a service for Sling Scripting that provides request-scoped Resource 
> Resolvers for scripting dependencies
> ---
>
> Key: SLING-6165
> URL: https://issues.apache.org/jira/browse/SLING-6165
> Project: Sling
>  Issue Type: New Feature
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Core 2.0.42, Scripting API 2.1.10
>
>
> A new Sling Scripting service ({{ScriptingResourceResolverFactory}}) should 
> be implemented in order to provide access to request-based 
> {{ResourceResolvers}} for solving script dependencies.
> The following two methods should be available:
> {noformat}
> /**
>  * Provides a request-scoped {@link ResourceResolver} with only read access 
> to the search paths. This resolver should be used for script 
>  * resolution in the context of the same request rendering process. The 
> {@code ResourceResolver} should not be closed by consumers (calling
>  * {@link ResourceResolver#close} doesn't do anything), since this service 
> will handle the closing operation automatically. The 
>  * {@code ResourceResolver} will be shared between scripting dependencies 
> that render parts of the response for the same request.
>  */
> ResourceResolver getRequestScopedResourceResolver()
> /**
>  * Provides a {@link ResourceResolver} with only read access to the search 
> paths. Once you're done processing {@link Resource}s with this 
>  * {@code ResourceResolver} make sure to close it.
>  */
> ResourceResolver getResourceResolver()
> {noformat}
> [sling-dev email 
> thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E]



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

RE: Stuff to work on (Was: sling attic / cleanup)

[Jason Bailey]

I'm able and willing to work on just about all of that. If I had the option I 
would probably focus on bug fixes, since I get a lot of satisfaction out of 
those.
 My problem with contributing is more of knowing where to focus than anything 
else, which is why it struck me when it was mentioned that some of the items 
that were going into the attic were going through lack of attention.

-Original Message-
From: Robert Munteanu [mailto:romb...@apache.org] 
Sent: Tuesday, October 18, 2016 4:48 PM
To: dev@sling.apache.org
Subject: Stuff to work on (Was: sling attic / cleanup)

On Tue, 2016-10-18 at 14:32 +, Jason Bailey wrote:
> Is there a list or something of modules that the sling developers 
> would like to have someone work on?

Well :-) What would you like to work on? Top of my head I can think of things 
that need work on

- automated testing
- performance checks/improvements
- bug fixes
- documentation
- design
- IDE Tooling
- CI setup
- Maven tooling
- migration to new parent pom

(and the list can go on)

What kind of things do you enjoy working on?

Robert


> 
> 
> 
> 
> -Original Message-
> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> Sent: Tuesday, October 18, 2016 10:04 AM
> To: dev 
> Subject: Re: sling attic / cleanup
> 
> Hi,
> 
> On Tue, Oct 18, 2016 at 3:53 PM, Robert Munteanu 
> wrote:
> > ...1) There are modules where we have people who think should move 
> > to the attic, but also others think the modules should be kept.
> > 
> > - contrib/auth/xing
> > - contrib/commons/html
> > - contrib/scripting/freemarker ..
> 
> 
> I don't have strong opinions on those but suggest moving at list the 
> first two to attic.
> 
> > ...2) We scheduled contrib/jcr/js for removal, but it's indirectly 
> > referenced from contrib/explorers/resourceeditor.
> > So we either keep both or move both to the attic. ...
> 
> 
> contrib/explorers/resourceeditor has changed very little since
> r1696091 from 2015-08-15 and the vast majority of commits are from 
> Sandro who hasn't been present here since January this year AFAICS.
> 
> So I suggest moving both modules to attic, it's easy to move back if 
> needed.
> 
> -Bertrand
> 

Re: [VOTE] Release Apache Sling Scheduler Support 2.5.2

[Carsten Ziegeler]

+1


 

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

Re: [VOTE] Release Apache Sling Scheduler Support 2.5.2

[Stefan Egli]

+1

Cheers,
Stefan

On 20/10/16 17:58, "Stefan Egli"  wrote:

>Hi,
>
>We solved 1 issue in the Scheduler Support 2.5.2 release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12337997
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1552/
>
>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 1552 /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.
>
>
>Cheers,
>Stefan
>
>

[jira] [Commented] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies

[Radu Cotescu (JIRA)]

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

Radu Cotescu commented on SLING-6165:
-

I think we can safely remove those two bundles as I've switched both of them to 
using a service user (SLING-5236).

> Expose a service for Sling Scripting that provides request-scoped Resource 
> Resolvers for scripting dependencies
> ---
>
> Key: SLING-6165
> URL: https://issues.apache.org/jira/browse/SLING-6165
> Project: Sling
>  Issue Type: New Feature
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting Core 2.0.42, Scripting API 2.1.10
>
>
> A new Sling Scripting service ({{ScriptingResourceResolverFactory}}) should 
> be implemented in order to provide access to request-based 
> {{ResourceResolvers}} for solving script dependencies.
> The following two methods should be available:
> {noformat}
> /**
>  * Provides a request-scoped {@link ResourceResolver} with only read access 
> to the search paths. This resolver should be used for script 
>  * resolution in the context of the same request rendering process. The 
> {@code ResourceResolver} should not be closed by consumers (calling
>  * {@link ResourceResolver#close} doesn't do anything), since this service 
> will handle the closing operation automatically. The 
>  * {@code ResourceResolver} will be shared between scripting dependencies 
> that render parts of the response for the same request.
>  */
> ResourceResolver getRequestScopedResourceResolver()
> /**
>  * Provides a {@link ResourceResolver} with only read access to the search 
> paths. Once you're done processing {@link Resource}s with this 
>  * {@code ResourceResolver} make sure to close it.
>  */
> ResourceResolver getResourceResolver()
> {noformat}
> [sling-dev email 
> thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E]



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

[VOTE] Release Apache Sling Scheduler Support 2.5.2

[Stefan Egli]

Hi,

We solved 1 issue in the Scheduler Support 2.5.2 release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12337997

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

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


Cheers,
Stefan

[jira] [Updated] (SLING-5387) Provide support for running singleton jobs on non leader cluster nodes also

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-5387:
---
Fix Version/s: (was: Commons Scheduler 2.5.2)
   Commons Scheduler 2.5.4

> Provide support for running singleton jobs on non leader cluster nodes also
> ---
>
> Key: SLING-5387
> URL: https://issues.apache.org/jira/browse/SLING-5387
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Chetan Mehrotra
> Fix For: Commons Scheduler 2.5.4
>
>
> With SLING-2979 support for running singleton jobs on specific instance was 
> provided. In most cases we want to run  a job as singleton and not want to 
> "pin" it to specific nodes. For this {{scheduler.runOn}} needs to be set to 
> {{SINGLE}}.
> However per [current 
> implementation|https://github.com/apache/sling/blob/org.apache.sling.commons.scheduler-2.4.14/src/main/java/org/apache/sling/commons/scheduler/impl/QuartzJobExecutor.java#L64]
>  {{SINGLE}} is treated as {{LEADER}}. This effectively causes *all singleton* 
> jobs to get executed on leader only thus putting extra load.
> For better utilization of cluster resources it should be possible to 
> distribute such singleton jobs on other cluster nodes and still ensure that 
> singleton contract is honoured!
> We would like to make use of this feature to ensure Oak AsyncIndexTask to run 
> on different cluster nodes (OAK-2749) 



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

[jira] [Updated] (SLING-5965) Metrics and a Health-Check for Scheduler to detect long-running Quartz-Jobs

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-5965:
---
Fix Version/s: (was: Commons Scheduler 2.5.2)
   Commons Scheduler 2.5.4

> Metrics and a Health-Check for Scheduler to detect long-running Quartz-Jobs
> ---
>
> Key: SLING-5965
> URL: https://issues.apache.org/jira/browse/SLING-5965
> Project: Sling
>  Issue Type: New Feature
>  Components: Commons
>Affects Versions: Commons Scheduler 2.5.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Commons Scheduler 2.5.4
>
> Attachments: SLING-5965.patch
>
>
> Sling Scheduler jobs (aka Quartz-Jobs) should typically be fast running jobs. 
> They are served from a thread-pool and should occupy that thread only for a 
> short amount of time.
> If there are 'misbehaving' quartz-jobs that run for a very long time, they 
> start to occupy threads from that thread-pool, thus have an influence on the 
> performance of other scheduled/quartz-jobs.
> We should have metrics (using 
> [sling.commons.metrics|https://sling.apache.org/documentation/bundles/metrics.html])
>  that provide information about internas of Sling Scheduler, such as average, 
> max etc duration of scheduled jobs, as well as how many jobs are currently 
> running and since when was the oldest job running.
> Based on this, a Health-Check can monitor the 'oldest job running' metric and 
> flag {{critical}} when eg the oldest job is older than {{60'000ms}} 
> (configurable, default).



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

[jira] [Closed] (SLING-6156) The JsUseProvider should use the sling-scripting service user for solving scripting dependencies

[Radu Cotescu (JIRA)]

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

Radu Cotescu closed SLING-6156.
---

> The JsUseProvider should use the sling-scripting service user for solving 
> scripting dependencies
> 
>
> Key: SLING-6156
> URL: https://issues.apache.org/jira/browse/SLING-6156
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL JS Use Provider 1.0.12
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
> Fix For: Scripting HTL JS Use Provider 1.0.16
>
>
> In SLING-5334 the {{JsUseProvider}} was modified for better handling of 
> script resolution for components using inheritance. However, the resolver 
> that's currently used for solving these dependencies is not the correct one, 
> since {{SlingScript}} resources will always use the request resource resolver.
> The fix is to switch to a resource resolver backed by the {{sling-scripting}} 
> service user.



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

[jira] [Resolved] (SLING-6178) quartz-scheduler: lower log.error to debug and move information to webconsole

[Stefan Egli (JIRA)]

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

Stefan Egli resolved SLING-6178.

Resolution: Fixed

Done in http://svn.apache.org/viewvc?view=revision=1765827

> quartz-scheduler: lower log.error to debug and move information to webconsole
> -
>
> Key: SLING-6178
> URL: https://issues.apache.org/jira/browse/SLING-6178
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Scheduler 2.5.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Commons Scheduler 2.5.2
>
>
> [Here|https://github.com/apache/sling/blob/d5112dac6832d6fc3260159ee6e3cd3f31f371a7/bundles/commons/scheduler/src/main/java/org/apache/sling/commons/scheduler/impl/QuartzJobExecutor.java#L78]
>  a log.error is issued when the scheduler would like to start a job that is 
> dependent on discovery. At startup and during bundle redeployment it is a 
> legal situation that scheduler is up and discovery not (yet). Therefore it 
> seems too loud to issue a log error.
> Thus lowering this to debug and instead providing this info in the webconsole 
> under status-slingscheduler instead.



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

[jira] [Created] (SLING-6178) quartz-scheduler: lower log.error to debug and move information to webconsole

[Stefan Egli (JIRA)]

Stefan Egli created SLING-6178:
--

 Summary: quartz-scheduler: lower log.error to debug and move 
information to webconsole
 Key: SLING-6178
 URL: https://issues.apache.org/jira/browse/SLING-6178
 Project: Sling
  Issue Type: Improvement
  Components: Commons
Affects Versions: Commons Scheduler 2.5.0
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Minor
 Fix For: Commons Scheduler 2.5.2


[Here|https://github.com/apache/sling/blob/d5112dac6832d6fc3260159ee6e3cd3f31f371a7/bundles/commons/scheduler/src/main/java/org/apache/sling/commons/scheduler/impl/QuartzJobExecutor.java#L78]
 a log.error is issued when the scheduler would like to start a job that is 
dependent on discovery. At startup and during bundle redeployment it is a legal 
situation that scheduler is up and discovery not (yet). Therefore it seems too 
loud to issue a log error.

Thus lowering this to debug and instead providing this info in the webconsole 
under status-slingscheduler instead.



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

[jira] [Commented] (SLING-6176) Installer: Persist optional error text per resource

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-6176:
-

[~kwin] Patches look basically good to me, however I think the old methods 
should not be deprecated, as there are many use cases where you don't want 
to/need to specify an error message, e.g. when you change the state to 
INSTALLED .

> Installer: Persist optional error text per resource
> ---
>
> Key: SLING-6176
> URL: https://issues.apache.org/jira/browse/SLING-6176
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Affects Versions: Installer Core 3.6.8, Installer Console 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Attachments: SLING-6176-console-v01.patch, SLING-6176-core-v01.patch
>
>
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. 
> This error text should be exposed through the web console. That way one could 
> easily determine (even afterwards) why a specific artifact was not installed 
> by the installer.
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



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

[RESULT][VOTE] Release Apache Sling Scripting HTL JS Use Provider 1.0.16

[Radu Cotescu]

Hi,

The release passes with 3 binding +1s from Carsten Ziegeler, Stefan Egli
and Daniel Klco.

Thanks,
Radu

[jira] [Closed] (SLING-6003) JavaScriptEngineFactory should move to new ResourceChangeListener API

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-6003.
---

> JavaScriptEngineFactory should move to new ResourceChangeListener API 
> --
>
> Key: SLING-6003
> URL: https://issues.apache.org/jira/browse/SLING-6003
> Project: Sling
>  Issue Type: Task
>  Components: Scripting
>Reporter: Hanish Bansal
>Assignee: Carsten Ziegeler
> Fix For: Scripting Java 2.1.0
>
> Attachments: SLING-6003.txt
>
>
> org.apache.sling.scripting.java.impl.JavaScriptEngineFactory currently 
> implements org.osgi.service.event.EventHandler Interface. We should start 
> using the new ResourceChangeListener API.
> See [0] for details :
> https://issues.apache.org/jira/browse/SLING-5994



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

[jira] [Closed] (SLING-6168) ServletContext is registered with wrong name

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-6168.
---

> ServletContext is registered with wrong name
> 
>
> Key: SLING-6168
> URL: https://issues.apache.org/jira/browse/SLING-6168
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Engine 2.5.0, Engine 2.6.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Engine 2.6.6
>
>
> Unfortunately , the ServletContext is not registered with the name 
> "org.apache.sling" as designed in SLING-5783, but with a class object of the 
> SlingMain class.



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

[jira] [Closed] (SLING-6004) JspScriptEngineFactory should move to new ResourceChangeListener API

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-6004.
---

> JspScriptEngineFactory should move to new ResourceChangeListener API  
> -
>
> Key: SLING-6004
> URL: https://issues.apache.org/jira/browse/SLING-6004
> Project: Sling
>  Issue Type: Task
>  Components: Scripting
>Reporter: Hanish Bansal
>Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.2.0
>
> Attachments: patch.txt
>
>
> org.apache.sling.scripting.jsp.JspScriptEngineFactory currently implements 
> org.osgi.service.event.EventHandler Interface. We should start using the new 
> ResourceChangeListener API.
> See [0] for details :
> https://issues.apache.org/jira/browse/SLING-5994



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

[jira] [Updated] (SLING-6176) Installer: Persist optional error text per resource

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated SLING-6176:
---
Attachment: SLING-6176-core-v01.patch
SLING-6176-console-v01.patch

Attached are two patches against installer core and console adding that 
additional attribute.
[~cziegeler] Can you have a look?

> Installer: Persist optional error text per resource
> ---
>
> Key: SLING-6176
> URL: https://issues.apache.org/jira/browse/SLING-6176
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Affects Versions: Installer Core 3.6.8, Installer Console 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Attachments: SLING-6176-console-v01.patch, SLING-6176-core-v01.patch
>
>
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. 
> This error text should be exposed through the web console. That way one could 
> easily determine (even afterwards) why a specific artifact was not installed 
> by the installer.
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



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

[jira] [Closed] (SLING-5522) Support servlet api 3.1 for jsps

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-5522.
---

> Support servlet api 3.1 for jsps
> 
>
> Key: SLING-5522
> URL: https://issues.apache.org/jira/browse/SLING-5522
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.2.0
>
> Attachments: patch.txt
>
>
> Currently jsps can only make use of the servlet 2.4 api



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

[jira] [Closed] (SLING-5784) Use service property to identify the ServletContext registered by Sling

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-5784.
---

> Use service property to identify the ServletContext registered by Sling
> ---
>
> Key: SLING-5784
> URL: https://issues.apache.org/jira/browse/SLING-5784
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting, Servlets
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.4.6, Scripting JSP 2.2.0, Scripting 
> Java 2.1.0
>
>
> The Sling Engine currently registers a ServletContext service, however 
> without any properties to identify this service. On the other hand, the 
> scripting bundles and the resolver simply take the first service they get. 
> There is no guarantee that this is really the context registered by Sling



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

[VOTE RESULT] Release Apache Sling Scripting JSP 2.2.0

[Carsten Ziegeler]

The vote passes with four  binding +1 votes

 Thanks
Carsten

 

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

[VOTE RESULT] Release Apache Sling Engine 2.6.6

[Carsten Ziegeler]

The vote passes with five  binding +1 votes

 Thanks
Carsten

 

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

[VOTE RESULT] Release Apache Sling Scripting Java 2.1.0

[Carsten Ziegeler]

The vote passes with four  binding +1 votes

 Thanks

Carsten

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

[jira] [Commented] (SLING-5973) HTMLSerializer not handling some unicode characters (emoji, etc.)

[Ben Fortuna (JIRA)]

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

Ben Fortuna commented on SLING-5973:


With thanks to the guys on the Cocoon project I was able to submit a patch to 
support HTML encoding of unicode surrogate pairs. I've verified with my test 
application that emojis are now displaying correctly with the rewriter enabled.

The patch will be included in the next Cocoon release, but in the meantime I 
was able to test with the latest snapshot build here:

https://repository.apache.org/content/groups/snapshots/org/apache/cocoon/cocoon-serializers-charsets/1.0.3-SNAPSHOT/


> HTMLSerializer not handling some unicode characters (emoji, etc.)
> -
>
> Key: SLING-5973
> URL: https://issues.apache.org/jira/browse/SLING-5973
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Ben Fortuna
> Attachments: emoji-no-sling-rewriter.png, 
> emoji-with-sling-rewriter.png
>
>
> I've noticed that when I have unicode special characters (e.g. emoji) in my 
> sling content and the sling rewriter is enabled the characters are not output 
> correctly to the browser. For example:
> {code}{code} becomes {code}{code}
> If I disable the rewriter pipeline the output is as expected.
> I've looked in the code and I suspect the issue is in the HTMLSerializer from 
> the Cocoon library, however I'm not sure why as it should be using the 
> default encoding for output (which is UTF-8). My rewriter pipeline is using 
> the default html-generator and html-serializer provided by sling.
> My code is available on GitHub here:
> https://github.com/Whistlepost/emojistrip
> It provides a very simple app/content project pair with some emoji characters 
> in the content (see src/main/resources/SLING-INF/content/phrases.json). Many 
> thanks.



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

Re: [VOTE] Release Apache Sling Log Tracer 1.0.2

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 7:38 AM, Carsten Ziegeler 
wrote:

> +1
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

Re: [VOTE] Release Apache Sling DataSource Provider 1.0.2

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 7:38 AM, Carsten Ziegeler 
wrote:

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

Re: [VOTE] Release Apache Sling Scripting HTL Engine 1.0.26

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 7:38 AM, Carsten Ziegeler 
wrote:

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

Re: [VOTE] Release Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 7:37 AM, Carsten Ziegeler 
wrote:

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

Re: [VOTE] Release Apache Sling Installer Core 3.7.0

[Daniel Klco]

+1

On Thu, Oct 20, 2016 at 6:13 AM, Radu Cotescu  wrote:

> +1
>
> On Thu, 20 Oct 2016 at 10:27 Carsten Ziegeler 
> wrote:
>
> > Please vote to approve this release:
> >
> >   [ ] +1 Approve the release
> >   [ ]  0 Don't care
> >   [ ] -1 Don't release, because ...
> >
>

Re: [VOTE] Release Apache Sling Log Tracer 1.0.2

[Carsten Ziegeler]

+1

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

Re: [VOTE] Release Apache Sling Scripting HTL Engine 1.0.26

[Carsten Ziegeler]

+1

 

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

Re: [VOTE] Release Apache Sling DataSource Provider 1.0.2

[Carsten Ziegeler]

+1

 

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

Re: [VOTE] Release Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0

[Carsten Ziegeler]

+1

 

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

[jira] [Assigned] (SLING-6176) Installer: Persist optional error text per resource

[Konrad Windszus (JIRA)]

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

Konrad Windszus reassigned SLING-6176:
--

Assignee: Konrad Windszus

> Installer: Persist optional error text per resource
> ---
>
> Key: SLING-6176
> URL: https://issues.apache.org/jira/browse/SLING-6176
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Affects Versions: Installer Core 3.6.8, Installer Console 1.0.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. 
> This error text should be exposed through the web console. That way one could 
> easily determine (even afterwards) why a specific artifact was not installed 
> by the installer.
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



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

[jira] [Updated] (SLING-5867) SlingRequestStatusHealthCheck should add timeout support

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated SLING-5867:
---
Assignee: (was: Konrad Windszus)

> SlingRequestStatusHealthCheck should add timeout support
> 
>
> Key: SLING-5867
> URL: https://issues.apache.org/jira/browse/SLING-5867
> Project: Sling
>  Issue Type: Bug
>  Components: Health Check
>Affects Versions: Health Check Support 1.0.4
>Reporter: Konrad Windszus
>
> Currently {{o.a.s.hc.support.impl.SlingRequestStatusHealthCheck}} just 
> synchronously calls {{SlingRequestProcessor.processResponse}}.
> That means in case of a non-returning response (e.g. caused by a deadlock 
> like SLING-5847) the health check will just timeout but never actually really 
> fail (even after a very long time).
> In this case it is good to create a dedicated timeout handling within the 
> {{SlingRequestStatusHealthCheck}} (separate from the timeout in 
> {{HealthCheckExecutorImpl}}) because for each individual request health check 
> configuration you might want to set different timeouts.



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

Re: sling attic / cleanup (Sitebuilder, Resource Editor)

[Sandro Boehme]

Hey Bertrand,

Am 20.10.16 um 09:12 schrieb Bertrand Delacretaz:

Hi Sandro,

On Wed, Oct 19, 2016 at 11:15 PM, Sandro Boehme  wrote:

...I'm still working on the Sitebuilder [1] and the resource editor and need
the js module for that...


ok, good to hear from you! No problem keeping those modules out of the attic.

-Bertrand


glad to read that. Some background and direction:
In the mean time I have one part time day a week where I can mostly work 
on it. My goal is to be able to use the Sitebuilder and Resource Editor 
for own websites. I will keep the Sitebuilder at GitHub and I guess I 
should rename it to not call it "Sling Sitebuilder" and only 
"Sitebuilder". But I would keep "sling" in the package name for now to 
avoid another refactoring.


Best,
Sandro

Re: [VOTE] Release Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0

[Chetan Mehrotra]

Hi Konrad,

Opened SLING-6177 for updating the docs. I had also marked SLING-6142
with 'docs-impacting' label earlier so that it does not get missed.
Hope to do that by next week
Chetan Mehrotra


On Thu, Oct 20, 2016 at 4:20 PM, Konrad Windszus  wrote:
> Can you add documentation about the grep feature in particular and about the 
> tailer in general to 
> https://sling.apache.org/documentation/development/logging.html? 
> 
> Thanks,
> Konrad
>> On 20 Oct 2016, at 12:18, Chetan Mehrotra  wrote:
>>
>> Hi,
>>
>> Apache Sling Commons Log 5.0.0  (5 Issues)
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12333765
>>
>> Apache Sling Commons Log WebConsole 1.0.0  (3 Issues)
>> https://issues.apache.org/jira/browse/SLING/fixforversion/12338425
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-1551/
>>
>> 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 1551 /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
>> Chetan Mehrotra
>>
>> Release Notes - Sling - Version Commons Log 5.0.0
>>
>> ** Bug
>>* [SLING-5756] - Async appender is not started upon reattach in
>> case of log config change
>>
>> ** Improvement
>>* [SLING-5092] - Missing Content type for 
>> system/console/slinglog/tailer.txt
>>* [SLING-5932] - Move Web Console Plugin to separate bundle
>>* [SLING-6144] - Update logback dependency to 1.1.7
>>
>> ** New Feature
>>* [SLING-6142] - Add grep like support in Log Tailer
>>
>> Release Notes - Sling - Version Commons Log WebConsole 1.0.0
>>
>> ** Improvement
>>* [SLING-5932] - Move Web Console Plugin to separate bundle
>>* [SLING-6144] - Update logback dependency to 1.1.7
>>
>> ** New Feature
>>* [SLING-6142] - Add grep like support in Log Tailer
>

[jira] [Created] (SLING-6177) Document the web tail and grep feature

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created SLING-6177:
--

 Summary: Document the web tail and grep feature
 Key: SLING-6177
 URL: https://issues.apache.org/jira/browse/SLING-6177
 Project: Sling
  Issue Type: Task
  Components: Documentation
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra


We should document the log grep (SLING-6142) and tail feature at [1]

[1] https://sling.apache.org/documentation/development/logging.html



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

Re: [VOTE] Release Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0

[Konrad Windszus]

Can you add documentation about the grep feature in particular and about the 
tailer in general to 
https://sling.apache.org/documentation/development/logging.html? 

Thanks,
Konrad
> On 20 Oct 2016, at 12:18, Chetan Mehrotra  wrote:
> 
> Hi,
> 
> Apache Sling Commons Log 5.0.0  (5 Issues)
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333765
> 
> Apache Sling Commons Log WebConsole 1.0.0  (3 Issues)
> https://issues.apache.org/jira/browse/SLING/fixforversion/12338425
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1551/
> 
> 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 1551 /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
> Chetan Mehrotra
> 
> Release Notes - Sling - Version Commons Log 5.0.0
> 
> ** Bug
>* [SLING-5756] - Async appender is not started upon reattach in
> case of log config change
> 
> ** Improvement
>* [SLING-5092] - Missing Content type for 
> system/console/slinglog/tailer.txt
>* [SLING-5932] - Move Web Console Plugin to separate bundle
>* [SLING-6144] - Update logback dependency to 1.1.7
> 
> ** New Feature
>* [SLING-6142] - Add grep like support in Log Tailer
> 
> Release Notes - Sling - Version Commons Log WebConsole 1.0.0
> 
> ** Improvement
>* [SLING-5932] - Move Web Console Plugin to separate bundle
>* [SLING-6144] - Update logback dependency to 1.1.7
> 
> ** New Feature
>* [SLING-6142] - Add grep like support in Log Tailer

[VOTE] Release Apache Sling Commons Log 5.0.0, Log WebConsole 1.0.0

[Chetan Mehrotra]

Hi,

Apache Sling Commons Log 5.0.0  (5 Issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12333765

Apache Sling Commons Log WebConsole 1.0.0  (3 Issues)
https://issues.apache.org/jira/browse/SLING/fixforversion/12338425

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

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 1551 /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
Chetan Mehrotra

Release Notes - Sling - Version Commons Log 5.0.0

** Bug
* [SLING-5756] - Async appender is not started upon reattach in
case of log config change

** Improvement
* [SLING-5092] - Missing Content type for system/console/slinglog/tailer.txt
* [SLING-5932] - Move Web Console Plugin to separate bundle
* [SLING-6144] - Update logback dependency to 1.1.7

** New Feature
* [SLING-6142] - Add grep like support in Log Tailer

Release Notes - Sling - Version Commons Log WebConsole 1.0.0

** Improvement
* [SLING-5932] - Move Web Console Plugin to separate bundle
* [SLING-6144] - Update logback dependency to 1.1.7

** New Feature
* [SLING-6142] - Add grep like support in Log Tailer

Re: [VOTE] Release Apache Sling Installer Core 3.7.0

[Radu Cotescu]

+1

On Thu, 20 Oct 2016 at 10:27 Carsten Ziegeler  wrote:

> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>

[jira] [Assigned] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[Konrad Windszus (JIRA)]

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

Konrad Windszus reassigned SLING-6175:
--

Assignee: Robert Munteanu  (was: Konrad Windszus)

> Sling IDE: Don't configure WTP natures by default for content-package projects
> --
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6175_v01.patch
>
>
> With the configurator being added in SLING-3100 there is always WTP natures 
> and according facets added for {{content-package}} projects. This is not 
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically 
> generated below the jcr_root folder 
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F & 
> http://stackoverflow.com/questions/14659891/m2e-wtp-error-path-target-m2e-wtp-web-resources-meta-inf-manifest-mf-no-such).
> Another drawback is that some validators (e.g. for javascript) are not 
> working reliably (because one package is not an autonomous piece of code and 
> often references code from outside the content package which is invisible to 
> Eclipse).
> Since {{content-packages}} are quite different from {{war}} projects I would 
> propose to only add those natures/facets if this is explicitly 
> configured/requested. Instead we should only add the native Sling IDE 
> natures/facets.
> The original idea behind making a {{content-package}} similar to a {{war}} 
> was to support code assist in JSPs better (i.e. for tag libraries). This 
> never reliably worked and therefore we should rather get rid of that approach.



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

Re: [VOTE] Release Apache Sling Log Tracer 1.0.2

[Chetan Mehrotra]

On Thu, Oct 20, 2016 at 3:17 PM, Chetan Mehrotra  wrote:
> * [SLING-5669] - Restrict usage of log tracing feature with access control

By mistake I missed moving this issue out. So ignore this issue for
this release vote

Chetan Mehrotra

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated SLING-6175:
---
Fix Version/s: Sling Eclipse IDE 1.1.2

> Sling IDE: Don't configure WTP natures by default for content-package projects
> --
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6175_v01.patch
>
>
> With the configurator being added in SLING-3100 there is always WTP natures 
> and according facets added for {{content-package}} projects. This is not 
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically 
> generated below the jcr_root folder 
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F & 
> http://stackoverflow.com/questions/14659891/m2e-wtp-error-path-target-m2e-wtp-web-resources-meta-inf-manifest-mf-no-such).
> Another drawback is that some validators (e.g. for javascript) are not 
> working reliably (because one package is not an autonomous piece of code and 
> often references code from outside the content package which is invisible to 
> Eclipse).
> Since {{content-packages}} are quite different from {{war}} projects I would 
> propose to only add those natures/facets if this is explicitly 
> configured/requested. Instead we should only add the native Sling IDE 
> natures/facets.
> The original idea behind making a {{content-package}} similar to a {{war}} 
> was to support code assist in JSPs better (i.e. for tag libraries). This 
> never reliably worked and therefore we should rather get rid of that approach.



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

[jira] [Updated] (SLING-6175) Sling IDE: Don't configure WTP natures by default for content-package projects

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated SLING-6175:
---
Attachment: SLING-6175_v01.patch

Attached is a patch which only configures WTP facets/natures in case the Maven 
property {{sling.ide.m2e.contentpackage.wtp.active}} is set to {{true}}.

> Sling IDE: Don't configure WTP natures by default for content-package projects
> --
>
> Key: SLING-6175
> URL: https://issues.apache.org/jira/browse/SLING-6175
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Attachments: SLING-6175_v01.patch
>
>
> With the configurator being added in SLING-3100 there is always WTP natures 
> and according facets added for {{content-package}} projects. This is not 
> always desired.
> It e.g. leads to the fact that a META-INF/MANIFEST.MF is automatically 
> generated below the jcr_root folder 
> (https://wiki.eclipse.org/M2E-WTP_FAQ#What_is_this_web_resources_folder.3F & 
> http://stackoverflow.com/questions/14659891/m2e-wtp-error-path-target-m2e-wtp-web-resources-meta-inf-manifest-mf-no-such).
> Another drawback is that some validators (e.g. for javascript) are not 
> working reliably (because one package is not an autonomous piece of code and 
> often references code from outside the content package which is invisible to 
> Eclipse).
> Since {{content-packages}} are quite different from {{war}} projects I would 
> propose to only add those natures/facets if this is explicitly 
> configured/requested. Instead we should only add the native Sling IDE 
> natures/facets.
> The original idea behind making a {{content-package}} similar to a {{war}} 
> was to support code assist in JSPs better (i.e. for tag libraries). This 
> never reliably worked and therefore we should rather get rid of that approach.



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

[jira] [Updated] (SLING-5669) Restrict usage of log tracing feature with access control

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra updated SLING-5669:
---
Fix Version/s: (was: Log Tracer 1.0.2)
   Log Tracer 1.0.4

> Restrict usage of log tracing feature with access control
> -
>
> Key: SLING-5669
> URL: https://issues.apache.org/jira/browse/SLING-5669
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: Log Tracer 1.0.4
>
>
> In SLING-5459 [~bdelacretaz] suggested that Tracer should provide a way to 
> secure use of the tracing feature to specific user.
> This can be done by having a specific path in content and check that current 
> user has read permission on that path. This would ensure that feature can be 
> more safely enabled. Note that even without this trace logs are only 
> accessible to admin user only.



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

[jira] [Resolved] (SLING-5932) Move Web Console Plugin to separate bundle

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra resolved SLING-5932.

Resolution: Fixed

> Move Web Console Plugin to separate bundle
> --
>
> Key: SLING-5932
> URL: https://issues.apache.org/jira/browse/SLING-5932
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Log 4.0.6
>Reporter: Carsten Ziegeler
>Assignee: Chetan Mehrotra
> Fix For: Commons Log 5.0.0, Commons Log WebConsole 1.0.0
>
>
> The log implementation currently contains a web console plugin which uses a 
> dynamic package import. Once the log impl is wired to a bundle providing the 
> servlet api and that bundle is updated/removed, it causes the log 
> implementation to refresh, which usually means a complete restart of the 
> system (as every bunde uses logging).
> We should reduce this coupling and remove any dependency to the servlet api 
> from the logging implementation



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

[VOTE] Release Apache Sling Log Tracer 1.0.2

[Chetan Mehrotra]

Hi,

We solved 6 issues for these releases:
https://issues.apache.org/jira/browse/SLING/fixforversion/12335584

** Bug
* [SLING-6089] - Log Tracer does not work with system having new
HTTP whiteboard implementation
* [SLING-6119] - Log parameters not captured correctly in few cases

** Improvement
* [SLING-5669] - Restrict usage of log tracing feature with access control
* [SLING-5762] - Relax Sling Log Tracer package imports
* [SLING-6118] - Handle empty tracer config header gracefully

** New Feature
* [SLING-6120] - Collect logger names which get hit for a given
request thread

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

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

Usage:
sh check_staged_release.sh 1550 /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
Chetan Mehrotra

[VOTE] Release Apache Sling DataSource Provider 1.0.2

[Chetan Mehrotra]

Hi,

We solved 1 issue for these releases:
https://issues.apache.org/jira/browse/SLING/fixforversion/12329308

** Bug
* [SLING-5879] - StatementCache interceptor configured by default
causes ResultSets to remain open

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

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

Usage:
sh check_staged_release.sh 1548 /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

[VOTE] Release Apache Sling Scripting HTL Engine 1.0.26

[Radu Cotescu]

Hi,

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

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

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

Usage:
sh check_staged_release.sh 1549 /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.

Cheers,
Radu

[jira] [Resolved] (SLING-6128) Sling IDE: Remove Lifecycle Mapping Extension Point for content-package

[Konrad Windszus (JIRA)]

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

Konrad Windszus resolved SLING-6128.

   Resolution: Fixed
Fix Version/s: Sling Eclipse IDE 1.1.2

Fixed in [r1765778|https://svn.apache.org/r1765778].

> Sling IDE: Remove Lifecycle Mapping Extension Point for content-package
> ---
>
> Key: SLING-6128
> URL: https://issues.apache.org/jira/browse/SLING-6128
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> The lifecycle mapping code for packaging {{content-package}} being added with 
> SLING-3100 is not necessary and should be removed. 
> Compare with http://www.mail-archive.com/dev@sling.apache.org/msg60234.html.



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

[jira] [Resolved] (SLING-6129) Sling IDE: Support bnd-maven-plugin as well

[Konrad Windszus (JIRA)]

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

Konrad Windszus resolved SLING-6129.

   Resolution: Fixed
Fix Version/s: Sling Eclipse IDE 1.1.2

Fixed in [r1765778|https://svn.apache.org/r1765778].

> Sling IDE: Support bnd-maven-plugin as well
> ---
>
> Key: SLING-6129
> URL: https://issues.apache.org/jira/browse/SLING-6129
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6129-v01.patch
>
>
> Currently the project configurator being added in SLING-3612 is only bound to 
> to the goals "manifest" and "bundle" of the maven-bundle-plugin. It should 
> also be automatically called for goal "bnd-process" of the bnd-maven-plugin 
> (https://github.com/bndtools/bnd/tree/master/maven/bnd-maven-plugin).



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

[jira] [Assigned] (SLING-6112) Make Sling IDE independent of m2e-tycho

[Konrad Windszus (JIRA)]

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

Konrad Windszus reassigned SLING-6112:
--

Assignee: Konrad Windszus  (was: Robert Munteanu)

> Make Sling IDE independent of m2e-tycho
> ---
>
> Key: SLING-6112
> URL: https://issues.apache.org/jira/browse/SLING-6112
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6112-v01.patch, SLING-6112-v02.patch, 
> SLING-6112-v03.patch
>
>
> Currently Sling IDE requires the installation of m2e-tycho. This was being 
> added in https://issues.apache.org/jira/browse/SLING-3608. Now that the 
> maven-bundle-plugin ships with m2e support OOTB (FELIX-4009) we should get 
> rid of that dependency.
> This is also important since newer versions of the maven-bundle-plugin 
> conflict with that extension 
> (https://issues.apache.org/jira/browse/FELIX-4009?focusedCommentId=15192263=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15192263).
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60112.html.



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

[jira] [Resolved] (SLING-6112) Make Sling IDE independent of m2e-tycho

[Konrad Windszus (JIRA)]

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

Konrad Windszus resolved SLING-6112.

Resolution: Fixed

Fixed in [r1765778|https://svn.apache.org/r1765778].

> Make Sling IDE independent of m2e-tycho
> ---
>
> Key: SLING-6112
> URL: https://issues.apache.org/jira/browse/SLING-6112
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: Sling Eclipse IDE 1.1.0
>Reporter: Konrad Windszus
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.1.2
>
> Attachments: SLING-6112-v01.patch, SLING-6112-v02.patch, 
> SLING-6112-v03.patch
>
>
> Currently Sling IDE requires the installation of m2e-tycho. This was being 
> added in https://issues.apache.org/jira/browse/SLING-3608. Now that the 
> maven-bundle-plugin ships with m2e support OOTB (FELIX-4009) we should get 
> rid of that dependency.
> This is also important since newer versions of the maven-bundle-plugin 
> conflict with that extension 
> (https://issues.apache.org/jira/browse/FELIX-4009?focusedCommentId=15192263=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15192263).
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60112.html.



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

Re: [VOTE] Release Apache Sling Installer Core 3.7.0

[Timothee Maret]

+1

2016-10-20 10:28 GMT+02:00 Carsten Ziegeler :

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>
>

[jira] [Updated] (SLING-6176) Installer: Persist optional error text per resource

[Konrad Windszus (JIRA)]

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

Konrad Windszus updated SLING-6176:
---
Description: 
Currently the OSGi installer web console will just expose a state like 
„Ignored“ or „Install“ in case a bundle/config/package could not be installed. 
It would be very helpful (especially in the context of SLING-5014) to 
additionally persist some error text on the last action, if it was not 
successful. 
This error text should be exposed through the web console. That way one could 
easily determine (even afterwards) why a specific artifact was not installed by 
the installer.

See also the discussion at 
http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.

  was:
Currently the OSGi installer web console will just expose a state like 
„Ignored“ or „Install“ in case a bundle/config/package could not be installed. 
It would be very helpful (especially in the context of SLING-5014) to 
additionally persist some error text on the last action, if it was not 
successful. This error text should be exposed through the web console. That way 
one could easily determine (even afterwards) why a specific artifact was not 
installed by the installer.

See also the discussion at 
http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.


> Installer: Persist optional error text per resource
> ---
>
> Key: SLING-6176
> URL: https://issues.apache.org/jira/browse/SLING-6176
> Project: Sling
>  Issue Type: Improvement
>  Components: Installer
>Affects Versions: Installer Core 3.6.8, Installer Console 1.0.0
>Reporter: Konrad Windszus
>
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. 
> This error text should be exposed through the web console. That way one could 
> easily determine (even afterwards) why a specific artifact was not installed 
> by the installer.
> See also the discussion at 
> http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



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

Re: OSGi Installer: Persist (optional) error text per resource

[Konrad Windszus]

I created https://issues.apache.org/jira/browse/SLING-6176 
 to track that.
Konrad

> On 20 Oct 2016, at 10:28, Carsten Ziegeler  wrote:
> 
> Konrad Windszus wrote
>> Currently the OSGi installer web console will just expose a state like 
>> „Ignored“ or „Install“ in case a bundle/config/package could not be 
>> installed. It would be very helpful (especially in the context of 
>> SLING-5014) to additionally persist some error text on the last action, if 
>> it was not successful. This error text should be exposed through the web 
>> console. That way one could easily determine (even afterwards) why a 
>> specific artifact was not installed by the installer.
>> WDYT?
> 
> Yes, that sounds like a great addition.
> 
> Carsten
> 
> 
> 
> -- 
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
> 

[jira] [Created] (SLING-6176) Installer: Persist optional error text per resource

[Konrad Windszus (JIRA)]

Konrad Windszus created SLING-6176:
--

 Summary: Installer: Persist optional error text per resource
 Key: SLING-6176
 URL: https://issues.apache.org/jira/browse/SLING-6176
 Project: Sling
  Issue Type: Improvement
  Components: Installer
Affects Versions: Installer Console 1.0.0, Installer Core 3.6.8
Reporter: Konrad Windszus


Currently the OSGi installer web console will just expose a state like 
„Ignored“ or „Install“ in case a bundle/config/package could not be installed. 
It would be very helpful (especially in the context of SLING-5014) to 
additionally persist some error text on the last action, if it was not 
successful. This error text should be exposed through the web console. That way 
one could easily determine (even afterwards) why a specific artifact was not 
installed by the installer.

See also the discussion at 
http://www.mail-archive.com/dev@sling.apache.org/msg60872.html.



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

Re: OSGi Installer: Persist (optional) error text per resource

[Carsten Ziegeler]

Konrad Windszus wrote
> Currently the OSGi installer web console will just expose a state like 
> „Ignored“ or „Install“ in case a bundle/config/package could not be 
> installed. It would be very helpful (especially in the context of SLING-5014) 
> to additionally persist some error text on the last action, if it was not 
> successful. This error text should be exposed through the web console. That 
> way one could easily determine (even afterwards) why a specific artifact was 
> not installed by the installer.
> WDYT?

Yes, that sounds like a great addition.

Carsten

 

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

Re: [VOTE] Release Apache Sling Installer Core 3.7.0

[Carsten Ziegeler]

+1

 

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

[VOTE] Release Apache Sling Installer Core 3.7.0

[Carsten Ziegeler]

Hi,

We solved 5 issues for these releases:
https://issues.apache.org/jira/browse/SLING/fixforversion/12335064

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

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

Usage:
sh check_staged_release.sh 1547 /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] [Updated] (SLING-5779) Packaged OSGi config intermittently do not get installed before bundle start

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-5779:

Fix Version/s: (was: Installer Core 3.7.0)
   Installer Core 3.7.2

> Packaged OSGi config intermittently do not get installed before bundle start
> 
>
> Key: SLING-5779
> URL: https://issues.apache.org/jira/browse/SLING-5779
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Reporter: Robert Munteanu
> Fix For: Installer Core 3.7.2
>
> Attachments: error.log.gz, stdout.log.gz
>
>
> (Setting version to Launchpad for now until we find out the root cause).
> From time to time I see the launchpad failing to start properly. The first 
> error that is visible is {noformat}10.06.2016 18:18:48.826 *ERROR* 
> [OsgiInstallerImpl] org.apache.jackrabbit.oak-lucene 
> [org.apache.jackrabbit.oak.plugins.index.lucene.LuceneIndexProviderService(31)]
>  The activate method has thrown an exception (java.lang.NullPointerException: 
> Index directory cannot be determined as neither index directory path 
> [localIndexDir] nor repository home [repository.home] defined)
> java.lang.NullPointerException: Index directory cannot be determined as 
> neither index directory path [localIndexDir] nor repository home 
> [repository.home] defined
> at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:236){noformat}
> That's weird since the provisioning model holds all the configurations and 
> the relevant bundles are present in the {{:boot}} feature → Start Level 1.
> My launchpad jar was built from r1747733 ( but of course SNAPSHOT 
> dependencies mean that someone else building the launchpad will not get the 
> same exact output ).



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

Re: sling attic / cleanup

[Bertrand Delacretaz]

Hi Sandro,

On Wed, Oct 19, 2016 at 11:15 PM, Sandro Boehme  wrote:
> ...I'm still working on the Sitebuilder [1] and the resource editor and need
> the js module for that...

ok, good to hear from you! No problem keeping those modules out of the attic.

-Bertrand

OSGi Installer: Persist (optional) error text per resource

[Konrad Windszus]

Currently the OSGi installer web console will just expose a state like 
„Ignored“ or „Install“ in case a bundle/config/package could not be installed. 
It would be very helpful (especially in the context of SLING-5014) to 
additionally persist some error text on the last action, if it was not 
successful. This error text should be exposed through the web console. That way 
one could easily determine (even afterwards) why a specific artifact was not 
installed by the installer.
WDYT?
Konrad