Sling Replication IP Clearance
Hi all, I just published the IP Clearance page for Sling Replication [1][2]. Please have a look and let me know if you think anything is wrong / missing, then I'll open the lazy consensus vote on general@incubator.a.o Thanks and regards, Tommaso [1] : http://incubator.apache.org/ip-clearance/sling-replication.html [2] : https://issues.apache.org/jira/browse/SLING-3254
Re: Sling Replication IP Clearance
LGTM Thanks Felix — Felix Meschberger | Principal Scientist | Adobe Am 29.11.2013 um 09:03 schrieb Tommaso Teofili tommaso.teof...@gmail.com: Hi all, I just published the IP Clearance page for Sling Replication [1][2]. Please have a look and let me know if you think anything is wrong / missing, then I'll open the lazy consensus vote on general@incubator.a.o Thanks and regards, Tommaso [1] : http://incubator.apache.org/ip-clearance/sling-replication.html [2] : https://issues.apache.org/jira/browse/SLING-3254
Re: [VOTE] Release Apache Sling discovery.impl 1.0.2
+1 Regards Felix — Felix Meschberger | Principal Scientist | Adobe Am 27.11.2013 um 12:22 schrieb Stefan Egli e...@adobe.com: Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12324866 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-013/ 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 013 /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
Re: Sling Replication IP Clearance
Hi, On Fri, Nov 29, 2013 at 9:03 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: ...[1] : http://incubator.apache.org/ip-clearance/sling-replication.html ... Looks good to me except links to votes which should point to http://mail-archives.apache.org/ - that information needs to be permanent, which markmail is not from our point of view. You'll probably want to use s.apache.org variants as the original ones are not really concise ;-) -Bertrand
Re: Sling Replication IP Clearance
Hi Bertrand, 2013/11/29 Bertrand Delacretaz bdelacre...@apache.org Hi, On Fri, Nov 29, 2013 at 9:03 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: ...[1] : http://incubator.apache.org/ip-clearance/sling-replication.html... Looks good to me except links to votes which should point to http://mail-archives.apache.org/ - that information needs to be permanent, which markmail is not from our point of view. You'll probably want to use s.apache.org variants as the original ones are not really concise ;-) good point, I've fixed the links as per your suggestions. Thanks, Tommaso -Bertrand
[jira] [Updated] (SLING-2892) Add simple paranoia check to detect duplicate sling.id in a cluster
[ https://issues.apache.org/jira/browse/SLING-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-2892: --- Fix Version/s: Discovery Impl 1.0.0 Add simple paranoia check to detect duplicate sling.id in a cluster --- Key: SLING-2892 URL: https://issues.apache.org/jira/browse/SLING-2892 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Discovery Impl 1.0.0 Reporter: Stefan Egli Assignee: Stefan Egli Fix For: Discovery Impl 1.0.0 Add a paranoia check to discovery.impl which detects a situation where more than one instance in a cluster is running with the same sling.id. Such a situation can for example occur, when the underlying repository-directory (which includes a sling.id.file) is copied to add an additional cluster slave. The suggested paranoia check works as follows: Each time a heartbeat is written to the repository, the last value of the heartbeat is checked to see if it matches the value written the last time. If there should be another instance in the same cluster using the same sling.id, it would have written the very same jcr-property but presumably with a slightly different timestamp. Should the value not match to the value last written, then a log.error is issued (with a reference to this bug and a possible fix for the situation). Note: this paranoia check is not 100% fool-proof, as it could be that the two instances try to write the very same heartbeat time (same millisecond). Yet it is considered at least a simple, stable mechanism to detect 99.9% of such cases. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-2901) Add robust paranoia check to detect duplicate sling.id in a cluster
[ https://issues.apache.org/jira/browse/SLING-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-2901: --- Fix Version/s: Discovery Impl 1.0.0 Add robust paranoia check to detect duplicate sling.id in a cluster --- Key: SLING-2901 URL: https://issues.apache.org/jira/browse/SLING-2901 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Discovery Impl 1.0.0 Reporter: Stefan Egli Assignee: Stefan Egli Fix For: Discovery Impl 1.0.0 Follow-up of SLING-2892 which added a simple (but not robust) paranoia check for duplicate sling.id detection in a cluster. A robust check can be achieved ontop of SLING-2892 by additionally setting a 'runtimeId' property (which is a UUID assigned at activation of the HeartbeatHandler) right after activation/at first time, and checking for changes of that property. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: [VOTE] Release Apache Sling discovery.impl 1.0.2
On Wednesday, November 27, 2013, Stefan Egli wrote: ...It should be there now... the release is signed with key DE41359E and I cannot find that key in any of https://people.apache.org/keys/group/sling.asc http://archive.apache.org/dist/sling/KEYS http://pgp.mit.edu/ where should I see it? Apart from that the release looks good to me, checked that the below source release builds fine, release artifacts match the corresponding svn tags and Apache file headers look good. Checked MD5 (org.apache.sling.discovery.impl-1.0.2-source-release.zip) = 6db157b29cb0c7070dc368005c977cf5 Several unit tests take a long time to run, making them integration tests might be convenient as people can then disable them selectively. But that doesn't impact the release. I'll wait for the key clarification before giving it my +1. -Bertrand
Re: [VOTE] Release Apache Sling discovery.impl 1.0.2
My bad. I must have used the wrong one of my two keys for signing. The two keys are at http://pgp.mit.edu:11371/pks/lookup?search=stefanegliop=index I have now added the second one to my apache profile too, where it should appear within a few hours. Or do I revoke and sign again? Cheers, Stefan On 11/29/13 11:20 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wednesday, November 27, 2013, Stefan Egli wrote: ...It should be there now... the release is signed with key DE41359E and I cannot find that key in any of https://people.apache.org/keys/group/sling.asc http://archive.apache.org/dist/sling/KEYS http://pgp.mit.edu/ where should I see it? Apart from that the release looks good to me, checked that the below source release builds fine, release artifacts match the corresponding svn tags and Apache file headers look good. Checked MD5 (org.apache.sling.discovery.impl-1.0.2-source-release.zip) = 6db157b29cb0c7070dc368005c977cf5 Several unit tests take a long time to run, making them integration tests might be convenient as people can then disable them selectively. But that doesn't impact the release. I'll wait for the key clarification before giving it my +1. -Bertrand
[VOTE] Release Apache Sling discovery.impl 1.0.2
On Friday, November 29, 2013, Stefan Egli wrote: ...I have now added the second one to my apache profile too, where it should appear within a few hours. Or do I revoke and sign again?... Signatures check ok with your http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x2B02392DDE41359E key, if it appears soon at https://people.apache.org/keys/group/sling.asc I'm ok. Here's my +1 for the release, thanks! -Bertrand
RE: [VOTE] Release Apache Sling discovery.impl 1.0.2
+1 best regards mike -Original Message- From: Stefan Egli [mailto:e...@adobe.com] Sent: Wednesday, November 27, 2013 3:03 PM To: dev@sling.apache.org Subject: Re: [VOTE] Release Apache Sling discovery.impl 1.0.2 Hi Ian, It should be there now. (It was 'in the pipeline somewhere'..) Cheers, Stefan On 11/27/13 2:47 PM, Ian Boston i...@tfd.co.uk wrote: Hi Could you add your signing key to the KEYS file please. Thanks Ian On 27 November 2013 11:59, Amit.. Gupta. amitg...@adobe.com wrote: +1 -Amit -Original Message- From: Stefan Egli [mailto:e...@adobe.com] Sent: 27 November 2013 16:53 To: dev@sling.apache.org Subject: [VOTE] Release Apache Sling discovery.impl 1.0.2 Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12324866 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-013/ 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 013 /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] [Resolved] (SLING-3258) [regression] Sling log support webconsole no longer links to logger configurations
[ https://issues.apache.org/jira/browse/SLING-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra resolved SLING-3258. Resolution: Fixed Fix Version/s: Commons Log 4.0.0 Added support in http://svn.apache.org/r1546580 [regression] Sling log support webconsole no longer links to logger configurations -- Key: SLING-3258 URL: https://issues.apache.org/jira/browse/SLING-3258 Project: Sling Issue Type: Bug Components: Commons Reporter: Alexander Klimetschek Assignee: Chetan Mehrotra Priority: Minor Labels: logback Fix For: Commons Log 4.0.0 The log support webconsole used to link to each logger configuration (the osgi configuration web console view). This is a useful feature to quickly find the right loggers and change log levels etc. and should be added back. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-2897) [LOG] Enhance web console plugin with edit feature
[ https://issues.apache.org/jira/browse/SLING-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835427#comment-13835427 ] Konrad Windszus commented on SLING-2897: [~chetanm] Would it be possible to consider that patch for Commons Log 4.0? I think it greatly enhances the configuration capabilities within the OSGi web console without too many code changes. [LOG] Enhance web console plugin with edit feature -- Key: SLING-2897 URL: https://issues.apache.org/jira/browse/SLING-2897 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons Log 3.0.0 Reporter: Bjoern Weide Priority: Minor Attachments: org.apache.sling.commons.log.patch, org.apache.sling.commons.log.patch The current web console plugin only lists the configured loggers but links for the actual configuration to the OSGi Configuration Manager. It should be improved so the logging configuration can be edited in the web console plugin directly. -- This message was sent by Atlassian JIRA (v6.1#6144)
buildbot failure in ASF Buildbot on sling-trunk-oak
The Buildbot has detected a new failure on builder sling-trunk-oak while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk-oak/builds/13 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: downstream Build Source Stamp: [branch sling/trunk] 1546580 Blamelist: chetanm BUILD FAILED: failed compile sincerely, -The Buildbot
[jira] [Resolved] (SLING-3257) Make logback packaging data in stacktraces configurable
[
https://issues.apache.org/jira/browse/SLING-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3257.
Resolution: Fixed
Fix Version/s: Commons Log 4.0.0
Added support in http://svn.apache.org/r1546601. A new property
{{org.apache.sling.commons.log.packagingDataEnabled}} is exposed as part of Log
Config Manager config
Make logback packaging data in stacktraces configurable
---
Key: SLING-3257
URL: https://issues.apache.org/jira/browse/SLING-3257
Project: Sling
Issue Type: Improvement
Components: Commons
Reporter: Alexander Klimetschek
Assignee: Chetan Mehrotra
Priority: Minor
Labels: logback
Fix For: Commons Log 4.0.0
The logback packaging information in stacktraces that was added with
SLING-3049 should be configurable, i.e. it should be possible to turn it on
or off.
Some stacktrace parsers (IDEs etc.) might not be able to parse it and it can
make traces harder to read, so it should IMO be an optional feature.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
buildbot success in ASF Buildbot on sling-trunk-oak
The Buildbot has detected a restored build on builder sling-trunk-oak while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/sling-trunk-oak/builds/14 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: osiris_ubuntu Build Reason: downstream Build Source Stamp: [branch sling/trunk] 1546601 Blamelist: chetanm Build succeeded! sincerely, -The Buildbot
[jira] [Assigned] (SLING-2897) [LOG] Enhance web console plugin with edit feature
[ https://issues.apache.org/jira/browse/SLING-2897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra reassigned SLING-2897: -- Assignee: Chetan Mehrotra [LOG] Enhance web console plugin with edit feature -- Key: SLING-2897 URL: https://issues.apache.org/jira/browse/SLING-2897 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: Commons Log 3.0.0 Reporter: Bjoern Weide Assignee: Chetan Mehrotra Priority: Minor Attachments: org.apache.sling.commons.log.patch, org.apache.sling.commons.log.patch The current web console plugin only lists the configured loggers but links for the actual configuration to the OSGi Configuration Manager. It should be improved so the logging configuration can be edited in the web console plugin directly. -- This message was sent by Atlassian JIRA (v6.1#6144)
Build failed in Jenkins: sling-trunk-1.6 #2049
See https://builds.apache.org/job/sling-trunk-1.6/2049/changes Changes: [chetanm] SLING-3257 - Make logback packaging data in stacktraces configurable Added property `org.apache.sling.commons.log.packagingDataEnabled` to configure the packaging data support. By default it would be enabled [chetanm] SLING-3258 - [regression] Sling log support webconsole no longer links to logger configurations Adding support for links to logger configs -- [...truncated 23833 lines...] [INFO] [INFO] --- maven-bundle-plugin:2.4.0:install (default-install) @ org.apache.sling.fsresource --- [INFO] Local OBR update disabled (enable with -DobrRepository) [INFO] [INFO] [INFO] Building Apache Sling javax.activation bundle 0.1.1-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.javax.activation --- [INFO] Executing tasks main: [INFO] Executed tasks [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.javax.activation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/extensions/javax.activation/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.javax.activation --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ org.apache.sling.javax.activation --- [INFO] Compiling 2 source files to https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/extensions/javax.activation/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.javax.activation --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/extensions/javax.activation/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ org.apache.sling.javax.activation --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ org.apache.sling.javax.activation --- [INFO] [JENKINS] Recording test results[INFO] --- animal-sniffer-maven-plugin:1.9:check (default) @ org.apache.sling.javax.activation --- [INFO] Checking unresolved references to org.codehaus.mojo.signature:java15:1.0 [INFO] [INFO] --- maven-bundle-plugin:2.4.0:bundle (default-bundle) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.javax.activation --- [INFO] Executing tasks main: [INFO] Executed tasks [WARNING] Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ org.apache.sling.javax.activation --- [INFO] Building jar: https://builds.apache.org/job/sling-trunk-1.6/ws/trunk/bundles/extensions/javax.activation/target/org.apache.sling.javax.activation-0.1.1-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-site-plugin:3.2:attach-descriptor (attach-descriptor) @ org.apache.sling.javax.activation --- [INFO] [INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ org.apache.sling.javax.activation --- [INFO] Checking legal files in: org.apache.sling.javax.activation-0.1.1-SNAPSHOT.jar [INFO] Checking legal files in: org.apache.sling.javax.activation-0.1.1-SNAPSHOT-sources.jar [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.apache.sling.javax.activation --- [INFO] Installing
Build failed in Jenkins: sling-trunk-1.7 #420
See https://builds.apache.org/job/sling-trunk-1.7/420/changes Changes: [chetanm] SLING-3257 - Make logback packaging data in stacktraces configurable Added property `org.apache.sling.commons.log.packagingDataEnabled` to configure the packaging data support. By default it would be enabled [chetanm] SLING-3258 - [regression] Sling log support webconsole no longer links to logger configurations Adding support for links to logger configs -- [...truncated 6751 lines...] [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ org.apache.sling.engine --- [INFO] Compiling 53 source files to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/classes [INFO] [INFO] --- maven-scr-plugin:1.14.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.engine --- [WARNING] https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/src/main/java/org/apache/sling/engine/impl/debug/RequestProgressTrackerLogFilter.java [0:0]: Property filter.scope in class org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter is set as private. This is redundant as no metatype will be generated. [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.engine.impl.SlingMainServlet.xml [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.engine.impl.log.RequestLogger.xml [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.engine.impl.log.RequestLoggerService.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.SlingSettingsServiceImpl.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.SlingMainServlet.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.log.RequestLoggerFilter.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.log.RequestLogger.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/scr-plugin-generated/OSGI-INF/org.apache.sling.engine.impl.log.RequestLoggerService.xml [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ org.apache.sling.engine --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ org.apache.sling.engine --- [INFO] Compiling 10 source files to https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ org.apache.sling.engine --- [INFO] Surefire report directory: https://builds.apache.org/job/sling-trunk-1.7/ws/trunk/bundles/engine/target/surefire-reports --- T E S T S --- Running org.apache.sling.engine.ResponseUtilTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec Running org.apache.sling.engine.impl.parameters.ContainerRequestParameterTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.apache.sling.engine.impl.parameters.UtilTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.044 sec Running org.apache.sling.engine.impl.log.CustomLogFormatTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec Running
