sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SLING-6545) slingstart-maven-plugin: By default do not redirect stderr and stdout of the sling server process to the one from the parent Maven process
Date Tue, 28 Feb 2017 07:23:45 GMT

     [ https://issues.apache.org/jira/browse/SLING-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Konrad Windszus closed SLING-6545.
----------------------------------

> slingstart-maven-plugin: By default do not redirect stderr and stdout of the sling server
process to the one from the parent Maven process
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6545
>                 URL: https://issues.apache.org/jira/browse/SLING-6545
>             Project: Sling
>          Issue Type: Improvement
>          Components: Tooling
>    Affects Versions: Slingstart Maven Plugin 1.7.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Slingstart Maven Plugin 1.7.2
>
>
> Currently the stdout and stderr from the Maven process is also used for the Sling Server
Process. That is a problem because even after one Mojo is done, the server is still running
and may still emit messages. Those overlap with the messages of the following Maven mojos.
Therefore the stdout and stderr of the Sling server should be redirected to a special file.
> The only drawback is, that in case of a central CI server, those additional files are
not that easy to evaluate (need to be downloaded separately). Still this is much better than
having overlapping log files of two independent processes (Maven and Sling Server).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message