[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3619: Fix Version/s: (was: JCR ContentLoader 2.4.2) > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco updated SLING-3619: Fix Version/s: (was: JCR ContentLoader 2.4.0) JCR ContentLoader 2.4.2 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.4.2 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman updated SLING-3619: --- Fix Version/s: (was: JCR ContentLoader 2.2.8) JCR ContentLoader 2.3.2 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.3.2 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason E Bailey updated SLING-3619: -- Fix Version/s: (was: JCR ContentLoader 2.2.6) JCR ContentLoader 2.2.8 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.2.8 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-3619: -- Fix Version/s: (was: JCR ContentLoader 2.2.4) JCR ContentLoader 2.2.6 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.2.6 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-3619: -- Fix Version/s: (was: JCR ContentLoader 2.2.0) JCR ContentLoader 2.2.2 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.2.2 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3619: Fix Version/s: JCR ContentLoader 2.2.0 > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > Fix For: JCR ContentLoader 2.2.0 > > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-3619: Summary: Content Loader should handle input errors gracefully (was: Content Loader Not working in current trunk build) > Content Loader should handle input errors gracefully > > > Key: SLING-3619 > URL: https://issues.apache.org/jira/browse/SLING-3619 > Project: Sling > Issue Type: Improvement > Components: JCR >Affects Versions: JCR ContentLoader 2.1.8 >Reporter: Yogesh Upadhyay >Assignee: Oliver Lietz >Priority: Minor > > After upgrading to latest sling jar file, content loader stopped working to > load content using Sling-Initial-Content. Getting following message in log > 29.05.2014 23:20:21.504 *INFO* [Background Install > /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzmgn/T/install277506169886207.tmp] > org.apache.sling.jcr.contentloader.internal.DefaultContentCreator > createFile: Cannot find content type for body.jsp, using > application/octet-stream -- This message was sent by Atlassian JIRA (v6.2#6252)
