[
https://issues.apache.org/jira/browse/SLING-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582063#comment-14582063
]
Konrad Windszus edited comment on SLING-4779 at 8/3/15 2:51 PM:
[
https://issues.apache.org/jira/browse/SLING-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek resolved SLING-4591.
--
Resolution: Fixed
Fix Version/s: API 2.10.0
Nice catch, thanks! Fixed in r1693875, as
On Fri, Jul 31, 2015 at 3:30 PM, Robert Munteanu romb...@apache.org wrote:
...Isn't that a Tomcat-specific exception [1]? It would be interesting to
see how they detect that this is due to the client aborting and
reuse/copy that approach...
Good idea, I'll have a look. We did have special
Hello,
The vote passed with five +1 from: Stefan Egli, Robert Munteanu, Antonio
Sanso, Carsten Ziegeler, Daniel Klco.
I will start promoting the release soon. @PMC: can you please move the
artifacts to dist?
Thanks,
Radu
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651711#comment-14651711
]
Robert Munteanu commented on SLING-4920:
The simplest way to deploy it is to
-
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4920:
---
Summary: content.query.json gives 404 (was: ontent.query.json gives 404)
content.query.json
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-4920.
Resolution: Not A Problem
[~swapnil.bagul89] - you need to deploy the
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651674#comment-14651674
]
Swapnil Bagul commented on SLING-4920:
--
Hi Robart
Thanks for your reply I am new to
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651711#comment-14651711
]
Robert Munteanu edited comment on SLING-4920 at 8/3/15 10:13 AM:
[
https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651718#comment-14651718
]
Robert Munteanu edited comment on SLING-2387 at 8/3/15 10:20 AM:
[
https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reopened SLING-2387:
Unforunately my script has added incorrect locations for the jars, reopening to
address the
[
https://issues.apache.org/jira/browse/SLING-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651736#comment-14651736
]
Swapnil Bagul commented on SLING-4920:
--
Thank you Robert Thank you so
[
https://issues.apache.org/jira/browse/SLING-4544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Richard resolved SLING-4544.
-
Resolution: Won't Fix
Closing as won't fix because in comparison to SLING-4596 and SLING-4611
[
https://issues.apache.org/jira/browse/SLING-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomek Rękawek reassigned SLING-4591:
Assignee: Tomek Rękawek
Performance: Consider using a faster empty map in
Swapnil Bagul created SLING-4920:
Summary: ontent.query.json gives 404
Key: SLING-4920
URL: https://issues.apache.org/jira/browse/SLING-4920
Project: Sling
Issue Type: Bug
Hi Robert
It seems that this commit causes up to ~900 tests to fail
(sporadically in two groups), both on Java 1.7 and 1.8. Before this we
had only few sporadically failing tests. Could you take a look if your
commit is the true cause or if the Jenkins builds give the wrong
impression[0,1].
[
https://issues.apache.org/jira/browse/SLING-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-2387.
Resolution: Fixed
Corrected the uri attributes for the ones which were incorrect
OBR at
On Mon, Aug 3, 2015 at 1:26 PM, Radu Cotescu r...@apache.org wrote:
Hello,
The vote passed with five +1 from: Stefan Egli, Robert Munteanu, Antonio
Sanso, Carsten Ziegeler, Daniel Klco.
I will start promoting the release soon. @PMC: can you please move the
artifacts to dist?
Done in
Hi,
Please remember to update the OBR file when releasing bundles [1] .
Besides the steps from the sling side, there's also an (experimental)
script I use for making sure all bundles from dist/ are present in the
OBR file [2].
Thanks,
Robert
[1]:
[
https://issues.apache.org/jira/browse/SLING-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651765#comment-14651765
]
Bertrand Delacretaz commented on SLING-3498:
Created SLING-4921 to handle the
On Fri, Jul 31, 2015 at 3:30 PM, Robert Munteanu romb...@apache.org wrote:
...It would be interesting to see how Tomcat detects that this is due to the
client aborting...
I have attached a proposed Sling engine patch to
https://issues.apache.org/jira/browse/SLING-4921 using the same
technique
[
https://issues.apache.org/jira/browse/SLING-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-4525.
---
XSS protection path mangling issue
--
Key: SLING-4525
[
https://issues.apache.org/jira/browse/SLING-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-4584.
---
Performance: XSSAPI.getValidHref should not be based on HTML filtering
[
https://issues.apache.org/jira/browse/SLING-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-4403.
---
XSS Configuration should allow caption tags
---
[
https://issues.apache.org/jira/browse/SLING-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-4557.
---
Add JSON and XML validation to the XSS Protection API
Hi,
in https://issues.apache.org/jira/browse/SLING-4779
https://issues.apache.org/jira/browse/SLING-4779 we had a discussion about
how to leverage a class from the bundle Commons OSGi 2.3 while still leaving
the dependency at 2.2.
The outcome was to use the approach listed in
Hi Konrad,
Is it possible to just embed the necessary classes rather than the whole
package? I think we do that in other cases and would (I think) eliminate
this issue.
Regards,
Justin
On Mon, Aug 3, 2015 at 8:26 AM Konrad Windszus konra...@gmx.de wrote:
Hi,
in
Bertrand Delacretaz created SLING-4921:
--
Summary: SlingMainServlet logs IOException at debug level only
Key: SLING-4921
URL: https://issues.apache.org/jira/browse/SLING-4921
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4921:
---
Attachment: SLING-4921.patch
Robert suggested looking at how Tomcat generates the
[
https://issues.apache.org/jira/browse/SLING-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4921:
---
Attachment: cae-stack-trace.txt
Attaching ClientAbortException stack trace for
Konrad Windszus created SLING-4922:
--
Summary: Validator should be allowed to get the resource on which
validation was triggered
Key: SLING-4922
URL: https://issues.apache.org/jira/browse/SLING-4922
The vote passed with 3 binding votes and 1 non-binding vote. Can a PMC help me
by promoting org.apache.sling.distribution.sample-0.1.2 and
org.apache.sling.distribution.core-0.1.6?
Thanks,
Marius
On 7/30/15, 1:02 PM, Carsten Ziegeler cziege...@apache.org wrote:
Am 30.07.15 um 09:17 schrieb
32 matches
Mail list logo
