[jira] [Commented] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224932#comment-17224932 ] Eric Norman commented on SLING-3533: I also don't know what the original concern was about, but it wouldn't hurt to have some additional test automation that focused on invalid or malformed input to make sure it is handled in a reasonable manner. > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224680#comment-17224680 ] Dan Klco commented on SLING-3533: - Honestly, I think the logging is acceptable, but I'm not entirely sure what was the concern. > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > Fix For: JCR ContentLoader 2.4.2 > > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224676#comment-17224676 ] Oliver Lietz commented on SLING-3533: - [~enorman], [~jeb], [~dklco], You guys have worked mainly on Content Loader in the past – is this issue still relevant or should we close it? > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > Fix For: JCR ContentLoader 2.4.2 > > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766898#comment-15766898 ] Oliver Lietz commented on SLING-3533: - Yes. All Content Loader issues assigned to me are still on my TODO, but Content Loader needs major cleanup and much more testing. > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: JCR ContentLoader 2.2.0 > > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLING-3533) improve error handling and logging in content loader
[ https://issues.apache.org/jira/browse/SLING-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766805#comment-15766805 ] Carsten Ziegeler commented on SLING-3533: - [~olli] Should we move this out of the 2.2.0 release schedule to not block it? > improve error handling and logging in content loader > > > Key: SLING-3533 > URL: https://issues.apache.org/jira/browse/SLING-3533 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.6 >Reporter: Oliver Lietz >Assignee: Oliver Lietz > Fix For: JCR ContentLoader 2.2.0 > > > handle errors more appropriate and use proper log levels -- This message was sent by Atlassian JIRA (v6.3.4#6332)
