[
https://issues.apache.org/jira/browse/SLING-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-5217.
Resolution: Fixed
Assignee: Robert Munteanu
The code looks good to me and I've
Robert Munteanu created SLING-5437:
--
Summary: The NoSQL providers should throw LoginException if the
connection to the NoSQL database can't be established
Key: SLING-5437
URL:
[
https://issues.apache.org/jira/browse/SLING-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-5437:
---
Attachment: 0001-SLING-5437-The-NoSQL-providers-should-throw-LoginExc.patch
Added a rough
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105445#comment-15105445
]
Robert Munteanu commented on SLING-5205:
After changing the OSGi config of the MongoDB provider,
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-5205:
---
Attachment: duplicate-mongodb-resource-provider.png
> Check for potential memory leaks
>
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-5205:
---
Assignee: Robert Munteanu
> Check for potential memory leaks
>
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105445#comment-15105445
]
Robert Munteanu edited comment on SLING-5205 at 1/18/16 3:41 PM:
-
After
[
https://issues.apache.org/jira/browse/SLING-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105105#comment-15105105
]
Bertrand Delacretaz commented on SLING-5414:
I've tried an approach where the slingstart maven
[
https://issues.apache.org/jira/browse/SLING-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105075#comment-15105075
]
Konrad Windszus commented on SLING-3891:
[~teofili] At first glance I couldn't find any
[
https://issues.apache.org/jira/browse/SLING-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5358:
---
Fix Version/s: Servlets Resolver 2.3.10
> Description for OSGi configuration of
>
[
https://issues.apache.org/jira/browse/SLING-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-5358:
---
Affects Version/s: (was: Servlets Resolver 2.3.10)
Servlets
[
https://issues.apache.org/jira/browse/SLING-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3891.
Resolution: Fixed
> Document Sling Content Distribution
>
[
https://issues.apache.org/jira/browse/SLING-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-5358.
Resolution: Fixed
Fixed in [r1725219|http://svn.apache.org/r1725219].
> Description for
[
https://issues.apache.org/jira/browse/SLING-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-4183:
---
Summary: Jcr Installer Provider only supports storing array values for OSGi
Component
Hi,
I was looking at
SLING-5217: Verify if login failures to resource providers are
handled correctly
and I tried to follow the logic behind the AuthType enum:
public enum AuthType { no, lazy, required }
The 'lazy' and 'required' values don't really 'partition' the providers
well IMO,
[
https://issues.apache.org/jira/browse/SLING-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3553.
Resolution: Fixed
Fix Version/s: Content Distribution Core 0.1.14
> Run FindBugs
Marius Petria created SLING-5436:
Summary: Do not move distribution packages to error queues after
connection problems
Key: SLING-5436
URL: https://issues.apache.org/jira/browse/SLING-5436
Project:
Tommaso Teofili created SLING-5439:
--
Summary: HttpEntity in SimpleHttpTransport should be consumed /
discarded
Key: SLING-5439
URL: https://issues.apache.org/jira/browse/SLING-5439
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria resolved SLING-5436.
--
Resolution: Fixed
> Do not move distribution packages to error queues after connection problems
Tommaso Teofili created SLING-5438:
--
Summary: Avoid reopening the JcrPackage during installation
Key: SLING-5438
URL: https://issues.apache.org/jira/browse/SLING-5438
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-5438.
Resolution: Fixed
fixed in r1725302
> Avoid reopening the JcrPackage during installation
>
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15105720#comment-15105720
]
Robert Munteanu commented on SLING-5205:
For the sake of being complete, here's a screenshot of
[
https://issues.apache.org/jira/browse/SLING-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-5205:
---
Attachment: shortest-path.png
> Check for potential memory leaks
>
23 matches
Mail list logo
