[
https://issues.apache.org/jira/browse/KARAF-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3532:
----------------------------------------
Component/s: eik-core
> Karaf EIK: karaf.lock not used from system properties
> -----------------------------------------------------
>
> Key: KARAF-3532
> URL: https://issues.apache.org/jira/browse/KARAF-3532
> Project: Karaf
> Issue Type: Bug
> Components: eik-core
> Affects Versions: 3.0.3
> Environment: Eclipse Luna, Karaf 3.0.3, latest Karaf EIK from github
> Reporter: Jochen Walz
> Priority: Minor
>
> Setting karaf.lock=false in system.properties or passing it with -D in the
> run configuration settings in Eclipse has no effect on startup behavior of
> Karaf with Karaf EIK. When starting more than one run configuration in
> Eclipse, the waiting for lock message is shown in karaf.log repeatedly.
> The reason is that in LockManager.java, lock(new Properties()) is used
> instead of reading the setting of karaf.lock from the system properties (e.g.
> lock(System.getProperties()) ).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
