[
https://issues.apache.org/jira/browse/KARAF-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147672#comment-13147672
]
Guillaume Nodet commented on KARAF-713:
---------------------------------------
Changes have been reverted partially (at least the Main class has been
reverted).
Christian, if you plan to work again on that, feel free to extract utility
methods in classes, but try to minimize changes to the whole main class, as
there are lots of cases that have been dealt with over the past years.
> Refactor karaf main
> -------------------
>
> Key: KARAF-713
> URL: https://issues.apache.org/jira/browse/KARAF-713
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
> Affects Versions: 2.2.2, 3.0.0
> Reporter: Christian Schneider
> Assignee: Guillaume Nodet
> Fix For: 3.0.0
>
>
> The karaf main project is currently not so well structured.
> The class Main has too many responsibilities and is too big (almost 1500
> lines).
> The lock classes are in the main package. They should be moved to a separate
> package.
> Proposal:
> create package lock and put everything about locking there. The case without
> locking should be handled as another lock implementation
> Split the Main class into setup of the framework and LifeCycleManager that
> handles the lock / start and stopping
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
