[
https://issues.apache.org/jira/browse/SLING-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria resolved SLING-4375.
--
Resolution: Fixed
Fix Version/s: Content Distribution 0.1.0
Assignee: Marius
See https://builds.apache.org/job/sling-trunk-1.6/changes
See https://builds.apache.org/job/sling-trunk-1.7/changes
Steven Walters created SLING-4376:
-
Summary: ResourceResolver-mock throws NullPointerException in
resolve when absPath = null
Key: SLING-4376
URL: https://issues.apache.org/jira/browse/SLING-4376
See https://builds.apache.org/job/sling-trunk-1.8/changes
Hi,
thanks for sharing this. The approach sounds reasonable, but it would
probably help to have a more concrete example for the content structure
including the resource type mappings.
Will /tenant/T/home only contain groups used define tenant membership? Or
will it also contain the actual users?
Hi,
This is the first thread I initiate on sling dev, so I apologize in advance
if I'm breaking any conventions.
I've written a bundle that allows sling component developers to quickly
define a hypermedia API for components. The tools contain a Sightly Use
class for Sightly components, but also
See https://builds.apache.org/job/sling-trunk-1.6/changes
See https://builds.apache.org/job/sling-trunk-1.7/changes
See https://builds.apache.org/job/sling-trunk-1.8/changes
Robert Munteanu created SLING-4374:
--
Summary: Intermittent error when publishing content
Key: SLING-4374
URL: https://issues.apache.org/jira/browse/SLING-4374
Project: Sling
Issue Type: Bug
Marius Petria created SLING-4375:
Summary: Expose distribution agent status
Key: SLING-4375
URL: https://issues.apache.org/jira/browse/SLING-4375
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-4374:
--
Assignee: Robert Munteanu
Intermittent error when publishing content
[
https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298425#comment-14298425
]
Konrad Windszus commented on SLING-4372:
[~fmeschbe] Thanks for supporting this.
[
https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298407#comment-14298407
]
Felix Meschberger commented on SLING-4372:
--
I like this idea and would welcome a
[
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso reassigned SLING-3854:
Assignee: Antonio Sanso
Add configuration option to restrict service user mapper to
[
https://issues.apache.org/jira/browse/SLING-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298385#comment-14298385
]
Konrad Windszus commented on SLING-3859:
The problem is basically that finalize
Konrad Windszus created SLING-4372:
--
Summary: The use of finalize in ResourceResolver leads to
performance issues
Key: SLING-4372
URL: https://issues.apache.org/jira/browse/SLING-4372
Project: Sling
See https://builds.apache.org/job/sling-trunk-1.7/changes
The question for me is whether we should rely on the dormant standard (which
did never release anything officially) 305, because that is not supported by
Eclipse or whether we should use something else?
Any ideas, opinions on that?
What is your experience with the JSR305 javax.annotation support
On Fri, Jan 30, 2015 at 2:55 PM, Konrad Windszus konra...@gmx.de wrote:
The question for me is whether we should rely on the dormant standard (which
did never release anything officially) 305, because that is not supported by
Eclipse or whether we should use something else?
Any ideas,
[
https://issues.apache.org/jira/browse/SLING-4294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14298495#comment-14298495
]
Antonio Sanso commented on SLING-4294:
--
added proposed patch with suggested changes
[
https://issues.apache.org/jira/browse/SLING-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-4373.
Resolution: Fixed
Calling ModelFactory.createModel with a null parameter for the adaptable
See https://builds.apache.org/job/sling-trunk-1.6/changes
+1 from my side. These annotations are useful and shouldn't cause any
problems.
Regards
Julian
On Friday, January 30, 2015, Konrad Windszus konra...@gmx.de wrote:
Hi,
the Sling API sometimes forces the developer to check for null results
e.g. SlingAdaptable.adaptTo and
[
https://issues.apache.org/jira/browse/SLING-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-4373:
---
Summary: Calling ModelFactory.createModel with a null parameter for the
adaptable leads to a
I am +1 on that, I think that, among its usage in analysis tools like
FindBugs, it helps very much in code readability, also major IDEs support
that and it's therefore easier not to mess up with e.g. some API having not
to return null and the likes.
My 2 cents,
Tommaso
2015-01-30 13:15 GMT+01:00
On Fri, Jan 30, 2015 at 2:15 PM, Konrad Windszus konra...@gmx.de wrote:
What about adding annotations like
https://code.google.com/p/jsr-305/source/browse/trunk/ri/src/main/java/javax/annotation/CheckForNull.java
28 matches
Mail list logo
