[jira] [Updated] (SLING-7552) SlingPostServlet error handling still insufficient

[ https://issues.apache.org/jira/browse/SLING-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Hoh updated SLING-7552: Labels: patch (was: ) > SlingPostServlet error handling still insufficient >

[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code

[ https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7581: --- Component/s: Scripting > Using data-sly-use with two classes with same name will generate

[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code

[ https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7581: --- Description: If you have an HTL file with two data-sly-use with classes with the same name

[jira] [Updated] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code

[ https://issues.apache.org/jira/browse/SLING-7581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-7581: --- Description: If you have an HTL file with two data-sly-use with classes with the same name

[jira] [Created] (SLING-7581) Using data-sly-use with two classes with same name will generate uncompilable code

Santiago García Pimentel created SLING-7581: --- Summary: Using data-sly-use with two classes with same name will generate uncompilable code Key: SLING-7581 URL:

[jira] [Comment Edited] (SLING-7534) Release policy - stop providing MD5 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437189#comment-16437189 ] Robert Munteanu edited comment on SLING-7534 at 4/13/18 11:10 AM: -- Since

[jira] [Commented] (SLING-7534) Release policy - stop providing MD5 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437189#comment-16437189 ] Robert Munteanu commented on SLING-7534: Since what matters is whatever is stored in

[jira] [Created] (SLING-7580) Servlets GET: JsonRendererServlet: ResourceTraversor: New optional request parameter appendChildResourceTypes should be provided to have the childresourceTypes array for

Avani Sarsani created SLING-7580: Summary: Servlets GET: JsonRendererServlet: ResourceTraversor: New optional request parameter appendChildResourceTypes should be provided to have the childresourceTypes array for each JsonObjectBuilder object in

[jira] [Commented] (SLING-7552) SlingPostServlet error handling still insufficient

[ https://issues.apache.org/jira/browse/SLING-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436965#comment-16436965 ] Jörg Hoh commented on SLING-7552: - I attached a patch, which just removes the error handling inside the

[jira] [Comment Edited] (SLING-7534) Release policy - stop providing MD5 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436956#comment-16436956 ] Bertrand Delacretaz edited comment on SLING-7534 at 4/13/18 7:35 AM: -

[jira] [Updated] (SLING-7552) SlingPostServlet error handling still insufficient

[ https://issues.apache.org/jira/browse/SLING-7552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Hoh updated SLING-7552: Attachment: SLING-7552-patch.diff > SlingPostServlet error handling still insufficient >

[jira] [Commented] (SLING-7534) Release policy - stop providing MD5 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436956#comment-16436956 ] Bertrand Delacretaz commented on SLING-7534: As per discussion at [1], it looks like it's

Re: [LAZY] Removing .md5 digest files in our releases folder

On Thu, Apr 12, 2018 at 5:51 PM, Konrad Windszus wrote: > ...We should just defer the actual deletion until we figured out how to > prevent MD5 generation for new releases in the first place... Ok, makes sense, I've made a note in SLING-7534 -Bertrand

[jira] [Commented] (SLING-7534) Release policy - stop providing MD5 signatures

[ https://issues.apache.org/jira/browse/SLING-7534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436925#comment-16436925 ] Bertrand Delacretaz commented on SLING-7534: Once this is clarified we should also remove