[
https://issues.apache.org/jira/browse/KARAF-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821067#comment-13821067
]
Christian Schneider commented on KARAF-2572:
--------------------------------------------
Well .. in fact this is true .. the unit test introduced a side effect as I set
a System property. This then influenced the other test depending on unit test
order.
I refactored the code so it can be tested without changing system properties.
> Karaf does not start if there is no log appender named out
> ----------------------------------------------------------
>
> Key: KARAF-2572
> URL: https://issues.apache.org/jira/browse/KARAF-2572
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Reporter: Christian Schneider
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
>
> When using a org.ops4j.pax.logging.cfg that does not contain a File appender
> with name "out" karaf does not start with a message about could not aquire
> file lock.
> This message is confusing as the real problem was that the
> BootStrapLogManager failed to initialize.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
