Re: [Metrics] Naming convention for MBeans registered by Sling Metrics

Hi, Could those generating the metrics use the full name, rather than expecting them to be automatically namespaced.? Rather like the way the Logger classes make no assumptions. That would be simpler, but perhaps more work for the developer. Best Regards Ian On 21 January 2016 at 05:28, Chetan

[jira] [Created] (SLING-5444) Display nameHints in webConsole for distribution factories

Marius Petria created SLING-5444: Summary: Display nameHints in webConsole for distribution factories Key: SLING-5444 URL: https://issues.apache.org/jira/browse/SLING-5444 Project: Sling

[jira] [Resolved] (SLING-5444) Display nameHints in webConsole for distribution factories

[ https://issues.apache.org/jira/browse/SLING-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-5444. -- Resolution: Fixed > Display nameHints in webConsole for distribution factories >

[jira] [Commented] (SLING-5444) Display nameHints in webConsole for distribution factories

[ https://issues.apache.org/jira/browse/SLING-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110262#comment-15110262 ] Marius Petria commented on SLING-5444: -- Committed revision 1725880. > Display nameHints in

[jira] [Resolved] (SLING-5446) DefaultSharedDistributionPackageBuilder should not be tight to the VLT builder

[ https://issues.apache.org/jira/browse/SLING-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-5446. Resolution: Fixed fixed in r1725986 > DefaultSharedDistributionPackageBuilder should not

[jira] [Created] (SLING-5446) DefaultSharedDistributionPackageBuilder should not be tight to the VLT builder

Tommaso Teofili created SLING-5446: -- Summary: DefaultSharedDistributionPackageBuilder should not be tight to the VLT builder Key: SLING-5446 URL: https://issues.apache.org/jira/browse/SLING-5446

[jira] [Updated] (SLING-5446) DefaultSharedDistributionPackageBuilder should not be tight to the VLT builder

[ https://issues.apache.org/jira/browse/SLING-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5446: --- Issue Type: Improvement (was: Bug) > DefaultSharedDistributionPackageBuilder should not be

Re: [Metrics] Naming convention for MBeans registered by Sling Metrics

> Could those generating the metrics use the full name, rather than expecting them to be automatically namespaced.? Note that this proposal is not for namespacing the metric name. Rather its for the JMX Domain name under which the MBean is registered. As for actual Metrics name currently its

[jira] [Updated] (SLING-5446) DefaultSharedDistributionPackageBuilder should not be tight to the VLT builder

[ https://issues.apache.org/jira/browse/SLING-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5446: --- Description: {{DefaultSharedDistributionPackageBuilder}} is used for fetching

[jira] [Created] (SLING-5445) XSSAPI#encodeForJSString is too restrictive

Radu Cotescu created SLING-5445: --- Summary: XSSAPI#encodeForJSString is too restrictive Key: SLING-5445 URL: https://issues.apache.org/jira/browse/SLING-5445 Project: Sling Issue Type: Bug

Re: Worthwhile to create a Sling CMS?

I recognized I accidently answered privately to Ondrej by hitting 'reply'. So here is my answer to him from two days ago: Hi Ondrej, Am 19.01.16 um 15:49 schrieb Ondrej Florian: Having yet another CMS for 'normal' people like Wix may not be worthwhile. I think it is not like Wix as it is Open

[jira] [Resolved] (SLING-5447) Enable FindBugs for the Sightly Scripting Engine

[ https://issues.apache.org/jira/browse/SLING-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-5447. - Resolution: Fixed Fixed in [r1726029|https://svn.apache.org/r1726029]. > Enable FindBugs for the

[RESULT][VOTE] Release Apache Sling Testing Utilities 2.0.24

Hi, The vote has passsed with the following result : +1 (binding) Robert Munteanu, Stefan Seifert, Dan Klco I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Thanks, Robert

[jira] [Created] (SLING-5447) Enable FindBugs for the Sightly Scripting Engine

Radu Cotescu created SLING-5447: --- Summary: Enable FindBugs for the Sightly Scripting Engine Key: SLING-5447 URL: https://issues.apache.org/jira/browse/SLING-5447 Project: Sling Issue Type:

[jira] [Resolved] (SLING-5445) XSSAPI#encodeForJSString is too restrictive

[ https://issues.apache.org/jira/browse/SLING-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-5445. - Resolution: Fixed Fixed in [r1726027|https://svn.apache.org/r1726027]. >

[jira] [Updated] (SLING-5448) AuthenticationInfoPostProcessor javadoc misleading

[ https://issues.apache.org/jira/browse/SLING-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Klimetschek updated SLING-5448: - Description: Currently, the [AuthenticationInfoPostProcessor javadoc

[jira] [Created] (SLING-5448) AuthenticationInfoPostProcessor javadoc misleading

Alexander Klimetschek created SLING-5448: Summary: AuthenticationInfoPostProcessor javadoc misleading Key: SLING-5448 URL: https://issues.apache.org/jira/browse/SLING-5448 Project: Sling

Re: svn commit: r1726029 - in /sling/trunk/bundles/scripting/sightly/engine: ./ src/main/java/org/apache/sling/scripting/sightly/impl/compiler/ src/main/java/org/apache/sling/scripting/sightly/impl/co

Hi Robert, Thanks for the heads up! How often is the analysis run? I see issues that have been fixed by the commit for SLING-5447. Cheers, Radu On Fri, 22 Jan 2016 at 07:38 Robert Munteanu wrote: > Hi Radu, > > On Thu, 2016-01-21 at 17:20 +, r...@apache.org wrote: > >

Re: svn commit: r1726029 - in /sling/trunk/bundles/scripting/sightly/engine: ./ src/main/java/org/apache/sling/scripting/sightly/impl/compiler/ src/main/java/org/apache/sling/scripting/sightly/impl/co

On Fri, 2016-01-22 at 07:50 +, Radu Cotescu wrote: > Hi Robert, > > Thanks for the heads up! How often is the analysis run? I see issues > that > have been fixed by the commit for SLING-5447. It polls daily for SCM changes, see build record at    

Re: svn commit: r1726029 - in /sling/trunk/bundles/scripting/sightly/engine: ./ src/main/java/org/apache/sling/scripting/sightly/impl/compiler/ src/main/java/org/apache/sling/scripting/sightly/impl/co

Hi Radu, On Thu, 2016-01-21 at 17:20 +, r...@apache.org wrote: > SLING-5447 - Enable FindBugs for the Sightly Scripting Engine > > * enabled FindBugs for the build process For the record you can also see the findbugs analysis results on the ASF Sonar instance: