Julian Sedding created SLING-4114:
-
Summary: Reduce amount of log output from
RequestProgressTrackerLogFilter
Key: SLING-4114
URL: https://issues.apache.org/jira/browse/SLING-4114
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Sedding updated SLING-4114:
--
Attachment: SLING-4114-jsedding.patch
Patch implementing above suggestions.
Reduce amount of
Hi all
The RequestProgressTrackerLogFilter allows logging the information
collected by the RequestProgressTracker at debug level. Since this can
amount to several undred lines logged per request, this may be
prohibiitive on a busy production system.
I propose to reduce the size of the log file
Robert Munteanu created SLING-4115:
--
Summary: Optimise rename handling
Key: SLING-4115
URL: https://issues.apache.org/jira/browse/SLING-4115
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188176#comment-14188176
]
Tommaso Teofili commented on SLING-4106:
in r1635078: added jsr305 annotations
[
https://issues.apache.org/jira/browse/SLING-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-4058.
Resolution: Fixed
At revision 1635083 all the active ResourceResolverTest tests
Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in productive Code. Do you see a way to workaround this
issue and/or give an estimation when this issue could be fixed? I'd help
See https://builds.apache.org/job/sling-trunk-1.8/384/changes
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.launchpad.test-services/384/changes
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/384/
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1099/
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.test-services/1099/changes
See https://builds.apache.org/job/sling-trunk-1.7/1099/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/1099/
i tried to run the integration tests for the event part on my (windows)
machines, sometimes the pass, sometimes they fail, not always with the same
result. but never because of a port mismatch.
today I started a new try:
* windows 7 + JDK 1.7: tests passed (but a showing frightening lot of
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/385/
See https://builds.apache.org/job/sling-trunk-1.8/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.base/1100/
See https://builds.apache.org/job/sling-trunk-1.7/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1100/
[
https://issues.apache.org/jira/browse/SLING-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188282#comment-14188282
]
Robert Munteanu commented on SLING-3221:
For the record, the discussion is at
Hi,
On Tue, Oct 28, 2014 at 8:57 PM, Carsten Ziegeler cziege...@apache.org wrote:
...This is a sporadic problem with Java 8 - it seems when a new Pax Exam
test starts, the old one isn't finished yet as the port is still in use
and the repository is locked
I have disabled the
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/386/changes
See https://builds.apache.org/job/sling-trunk-1.8/386/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.event/1101/changes
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad.testing/1101/
See https://builds.apache.org/job/sling-trunk-1.7/changes
Am 29.10.14 um 13:32 schrieb Bertrand Delacretaz:
Hi,
On Tue, Oct 28, 2014 at 8:57 PM, Carsten Ziegeler cziege...@apache.org
wrote:
...This is a sporadic problem with Java 8 - it seems when a new Pax Exam
test starts, the old one isn't finished yet as the port is still in use
and the
Am 29.10.14 um 12:25 schrieb Stefan Seifert:
i tried to run the integration tests for the event part on my (windows)
machines, sometimes the pass, sometimes they fail, not always with the same
result. but never because of a port mismatch.
today I started a new try:
* windows 7 + JDK
See
https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.core/1317/
Am 29.10.14 um 11:13 schrieb Dominik Süß:
Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in productive Code. Do you see a way to workaround this
issue and/or give an
See
https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.event/1102/changes
See https://builds.apache.org/job/sling-trunk-1.7/1102/changes
See https://builds.apache.org/job/sling-trunk-1.8/387/changes
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/387/changes
[
https://issues.apache.org/jira/browse/SLING-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-4109.
Resolution: Fixed
Assignee: Marius Petria
Use safe ids for replication packages such
See
https://builds.apache.org/job/sling-contrib-1.6/org.apache.sling$org.apache.sling.replication.core/1318/
[
https://issues.apache.org/jira/browse/SLING-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188514#comment-14188514
]
Sandro Boehme commented on SLING-4001:
--
++ Building without OSGi OBR deployment ++
See
https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.event/388/
See https://builds.apache.org/job/sling-trunk-1.8/388/changes
[
https://issues.apache.org/jira/browse/SLING-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert reassigned SLING-4112:
-
Assignee: Stefan Seifert
Sling Models: Optimize performance when read sling models
Robert Munteanu created SLING-4116:
--
Summary: Content length check in JCRNodeResourceMetadata triggers
javax.jcr.ItemNotFoundException: No primary item present on node
Key: SLING-4116
URL:
On Wed, Oct 29, 2014 at 5:24 PM, Carsten Ziegeler cziege...@apache.org wrote:
Am 29.10.14 um 11:13 schrieb Dominik Süß:
Hi Carsten,
thanks for your quick feedback - yes it works without functional
degradations but it actually spams the error.log with INFO messages which
is not acceptable in
Sandro Boehme created SLING-4117:
Summary: 'mountByFS=true' doesn't work a second time
Key: SLING-4117
URL: https://issues.apache.org/jira/browse/SLING-4117
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandro Boehme updated SLING-4117:
-
Attachment: SLING-4117-patch.txt
'mountByFS=true' doesn't work a second time
45 matches
Mail list logo