[jira] [Resolved] (SLING-6466) Rename sub service users

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6466. - Resolution: Fixed Changed the sub service name as suggested above in rev 1779570 Updated

[jira] [Updated] (SLING-6466) Rename sub service users

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6466: Summary: Rename sub service users (was: Rename system user sling-readall and sub service

[jira] [Updated] (SLING-6466) Rename system user sling-readall and sub service read

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6466: Component/s: (was: Karaf) (was: JCR) > Rename system user

[jira] [Assigned] (SLING-6466) Rename system user sling-readall and sub service read

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-6466: --- Assignee: Carsten Ziegeler > Rename system user sling-readall and sub service read >

Re: [VOTE] Release Apache Sling File System Resource Provider 1.2.2, Maven Sling Plugin 2.1.10

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

RE: [VOTE] Release Apache Sling File System Resource Provider 1.2.2, Maven Sling Plugin 2.1.10

+1

[VOTE] Release Apache Sling File System Resource Provider 1.2.2, Maven Sling Plugin 2.1.10

Hi, Apache Sling File System Resource Provider 1.2.2*) (4 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12328647 *) version 1.2.0 was skipped due to an issue found after release Apache Sling Maven Sling Plugin 2.1.10 (1 issue)

Re: MetricsService question.

Hi, I followed your suggestion on using a listener and it works ok. Not too much extra code for the reporter. No need for another API. Thanks for the pointers. Best Regards Ian On 19 January 2017 at 12:36, Ian Boston wrote: > On restarting the instance > > @Reference > private

[jira] [Resolved] (SLING-5759) Distribution agents cannot be created via API

[ https://issues.apache.org/jira/browse/SLING-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-5759. Resolution: Fixed Fix Version/s: Content Distribution 0.2.0 > Distribution agents

[jira] [Resolved] (SLING-3311) Add facilities to monitor replication status

[ https://issues.apache.org/jira/browse/SLING-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-3311. Resolution: Fixed Fix Version/s: Content Distribution 0.2.0 > Add facilities to

[jira] [Commented] (SLING-4575) Failure registering MBean HealthCheckMBean [healthCheck=org.apache.sling.distribution.monitor.DistributionQueueHealthCheck@...]

[ https://issues.apache.org/jira/browse/SLING-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830035#comment-15830035 ] Tommaso Teofili commented on SLING-4575: I think this has been resolved already, [~olli] WDYT? >

[jira] [Resolved] (SLING-5915) Fix IT failures in Content Distribution

[ https://issues.apache.org/jira/browse/SLING-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-5915. Resolution: Duplicate > Fix IT failures in Content Distribution >

[jira] [Resolved] (SLING-6391) DefaultDistributionConfigurationManager overrides existing persisted properties

[ https://issues.apache.org/jira/browse/SLING-6391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6391. Resolution: Fixed > DefaultDistributionConfigurationManager overrides existing persisted >

[jira] [Commented] (SLING-6251) SCD integration tests fail due to blocked loginAdministrative

[ https://issues.apache.org/jira/browse/SLING-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15830025#comment-15830025 ] Tommaso Teofili commented on SLING-6251: we have removed _loginAdmin_ and they now pass thanks to

[jira] [Resolved] (SLING-6251) SCD integration tests fail due to blocked loginAdministrative

[ https://issues.apache.org/jira/browse/SLING-6251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6251. Resolution: Fixed Fix Version/s: Content Distribution 0.2.0 > SCD integration tests

[jira] [Commented] (SLING-6473) Create a VersionResolver that provides versions from provisioning model files

[ https://issues.apache.org/jira/browse/SLING-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829945#comment-15829945 ] Oliver Lietz commented on SLING-6473: - bq. sometimes you need the bleeding edge stuff, even for

[jira] [Commented] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829918#comment-15829918 ] Nino Martinez commented on SLING-6474: -- hmm yes, I checked the latest snapshots here: None of them

[jira] [Resolved] (SLING-6475) Distribution IT test fail on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret resolved SLING-6475. --- Resolution: Fixed Fix Version/s: Content Distribution Core 0.1.20 > Distribution IT

Re: MetricsService question.

On restarting the instance @Reference private MetricRegistry metricRegistry is satisfied, no idea why. ... although it binds to the first one loosing data in Sling. Perhaps that also why there are no Metrics from Sling exported to JMX, only Oak metrics, or no metrics in Sling in the version I

Re: MetricsService question.

Hi, On 19 January 2017 at 11:28, Chetan Mehrotra wrote: > Thinking further I think Ian's problem is around dealing with multiple > MetricRegistry instance for each reporter implementation. I think that > we can simplify by providing a MetricRegistryProvider which

[jira] [Commented] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829789#comment-15829789 ] Chetan Mehrotra commented on SLING-6474: I think its already 3.2.0 {noformat} mvn

[jira] [Commented] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829785#comment-15829785 ] Nino Martinez commented on SLING-6474: -- Yes, but I think it is as trivial as upgrading to the

[jira] [Updated] (SLING-6343) Sling IDE: Publishing failures do no report the correct synchronization state of the module

[ https://issues.apache.org/jira/browse/SLING-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6343: --- Assignee: Konrad Windszus > Sling IDE: Publishing failures do no report the correct

Re: MetricsService question.

Thinking further I think Ian's problem is around dealing with multiple MetricRegistry instance for each reporter implementation. I think that we can simplify by providing a MetricRegistryProvider which provides a registry instance which contains metrices from all MetricRegistries interface

[jira] [Commented] (SLING-6475) Distribution IT test fail on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829752#comment-15829752 ] Timothee Maret commented on SLING-6475: --- After commits {{r1757192}} (and others), the tests pass

Re: MetricsService question.

On Thu, Jan 19, 2017 at 4:49 PM, Bertrand Delacretaz wrote: > @Reference > private MetricsServiceProvider msp; Some confusion ... there is only 1 MetricsService [1] and that too is under Sling package namespace. So we do not need any abstraction. Chetan Mehrotra [1]

Re: MetricsService question.

On Thu, Jan 19, 2017 at 12:04 PM, Ian Boston wrote: > ...It could be so simple to have 1 bundle exposing a service, adaptable to the > required MetricsRegistry singleton for reporting... IIUC what you suggest can also help with namespacing the metrics, which is important as we

Re: MetricsService question.

On Thu, Jan 19, 2017 at 4:34 PM, Ian Boston wrote: > I also fear that there will be multiple APIs, all nearly the same, The recommended API is the one in Sling Commons Metrics. Oak one is internal to use in Oak and should not be used by other components. This is because

Re: MetricsService question.

Hi, On 19 January 2017 at 09:26, Chetan Mehrotra wrote: > On Thu, Jan 19, 2017 at 2:48 PM, Ian Boston wrote: > > > > Is the intention that [1] should use the same approach as [2] so that > there > > is 1 MetricsRegistry per JVM ? > > No. Sling

[jira] [Comment Edited] (SLING-6478) Add a Sling model annotation+injector for request parameters

[ https://issues.apache.org/jira/browse/SLING-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829705#comment-15829705 ] Christophe Jelger edited comment on SLING-6478 at 1/19/17 10:46 AM: I

[jira] [Commented] (SLING-6478) Add a Sling model annotation+injector for request parameters

[ https://issues.apache.org/jira/browse/SLING-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829705#comment-15829705 ] Christophe Jelger commented on SLING-6478: -- I just attached a diff to add that functionality.

[jira] [Updated] (SLING-6478) Add a Sling model annotation+injector for request parameters

[ https://issues.apache.org/jira/browse/SLING-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christophe Jelger updated SLING-6478: - Attachment: SLING-6478-patch.diff > Add a Sling model annotation+injector for request

[jira] [Commented] (SLING-6473) Create a VersionResolver that provides versions from provisioning model files

[ https://issues.apache.org/jira/browse/SLING-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829696#comment-15829696 ] Bertrand Delacretaz commented on SLING-6473: bq. The ProvisioningModelVersionResolver defeats

[jira] [Created] (SLING-6478) Add a Sling model annotation+injector for request parameters

Christophe Jelger created SLING-6478: Summary: Add a Sling model annotation+injector for request parameters Key: SLING-6478 URL: https://issues.apache.org/jira/browse/SLING-6478 Project: Sling

[jira] [Resolved] (SLING-6477) Distributing with sling.jcr.api 2.2.0 should not throw NSME

[ https://issues.apache.org/jira/browse/SLING-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6477. Resolution: Fixed fixed in r1779444. > Distributing with sling.jcr.api 2.2.0 should not

[jira] [Created] (SLING-6477) Distributing with sling.jcr.api 2.2.0 should not throw NSME

Tommaso Teofili created SLING-6477: -- Summary: Distributing with sling.jcr.api 2.2.0 should not throw NSME Key: SLING-6477 URL: https://issues.apache.org/jira/browse/SLING-6477 Project: Sling

[jira] [Commented] (SLING-6466) Rename system user sling-readall and sub service read

[ https://issues.apache.org/jira/browse/SLING-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829662#comment-15829662 ] Carsten Ziegeler commented on SLING-6466: - [~olli] So my recommendation would be recommended:

Re: MetricsService question.

On Thu, Jan 19, 2017 at 2:48 PM, Ian Boston wrote: > > Is the intention that [1] should use the same approach as [2] so that there > is 1 MetricsRegistry per JVM ? No. Sling Metrics creates and manages its own MetricRegistry and registers it in OSGi with a "name" service

MetricsService question.

Hi, Is the intention that [1] should use the same approach as [2] so that there is 1 MetricsRegistry per JVM ? ie Check for a MetricsRegistry as a service, and if not present create one, so that there is only 1 which reporters can report on. I am wondering how this will be made thread safe, as

[jira] [Updated] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-6474: --- Issue Type: Improvement (was: Bug) > Commons Metrics DOES not declare provide capability for

[jira] [Commented] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829535#comment-15829535 ] Chetan Mehrotra commented on SLING-6474: [~nmwael] I am not much well versed with capability part

[jira] [Assigned] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned SLING-6474: -- Assignee: Chetan Mehrotra > Commons Metrics DOES not declare provide capability for

[jira] [Updated] (SLING-6474) Commons Metrics DOES not declare provide capability for Metrics service

[ https://issues.apache.org/jira/browse/SLING-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-6474: --- Fix Version/s: Commons Metrics 1.2.2 > Commons Metrics DOES not declare provide capability

[jira] [Updated] (SLING-6476) [HTL] data-sly-resource transforms resources with dots in their paths to SyntheticResources

[ https://issues.apache.org/jira/browse/SLING-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6476: Summary: [HTL] data-sly-resource transforms resources with dots in their paths to

[jira] [Updated] (SLING-6476) Sightly and JSP include differ for resource paths with multiple dots

[ https://issues.apache.org/jira/browse/SLING-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6476: Fix Version/s: Scripting HTL Engine 1.0.32 > Sightly and JSP include differ for resource paths with

[jira] [Updated] (SLING-6476) Sightly and JSP include differ for resource paths with multiple dots

[ https://issues.apache.org/jira/browse/SLING-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6476: Affects Version/s: Scripting Sightly Engine 1.0.0 > Sightly and JSP include differ for resource

[jira] [Assigned] (SLING-6476) Sightly and JSP include differ for resource paths with multiple dots

[ https://issues.apache.org/jira/browse/SLING-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reassigned SLING-6476: --- Assignee: Radu Cotescu > Sightly and JSP include differ for resource paths with multiple