You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (Jira)" <ji...@apache.org> on 2021/03/23 09:09:00 UTC

[jira] [Commented] (SLING-10250) Sending a test message leads to an error

    [ https://issues.apache.org/jira/browse/SLING-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306910#comment-17306910 ] 

Timothee Maret commented on SLING-10250:
----------------------------------------

This issue was noticed and fixed [here|https://issues.apache.org/jira/secure/EditComment!default.jspa?id=13352677&commentId=17300288].

[~cschneider] Apache Sling does hold the code of the UI you are referencing here and we don't maintain internal releases. We may stick to the existing versioning scheme and release process.

> Sending a test message leads to an error
> ----------------------------------------
>
>                 Key: SLING-10250
>                 URL: https://issues.apache.org/jira/browse/SLING-10250
>             Project: Sling
>          Issue Type: Bug
>          Components: Content Distribution
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>            Priority: Critical
>             Fix For: Content Distribution Journal Core 0.1.18
>
>         Attachments: screenshot-1.png
>
>
> The commit below from https://issues.apache.org/jira/browse/SLING-10066 (2021-02-11 16:44:16) introduced an error where a distribution without paths throws an exception.
>  This occurs when sending a test request. The issue is visible in the UI as "An error has occured while attempting to deliver a test package".
> The issue was fixed in a commit on the same sling issue on (2021-03-12 18:08:35). 
> Unfortunately the code went into internal releases. So I wanted to document it existing here as a reference.
> Internal releases affected are:
>  - org.apache.sling.distribution.journal-0.1.17-T20210211
> - org.apache.sling.distribution.journal-0.1.17-T20210301
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)