[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] Jetty Plugin Functionality / Getting rid of Jetty Hightide release at codehaus
|
On 8 November 2011 23:58, Thomas Becker
<tbecker@xxxxxxxxxxx> wrote:
I think I personally prefer the most simple approach and have the user be responsible of keeping plugin customizations at a safe place when removing plugins. The normal use case is that a user needs a standard jetty installation. Whenever he needs a plugin he installs it with a single command. The plugin is then enabled by default. He should only need to remove the plugin if he doesn't need it anymore and in that case he doesn't need his customizations anymore.
Thomas,
I don't think simplicity is the right measure here. Whatever we come up with, we can have a simple install/uninstall tool that hides whatever complexity exists.
I'd rather to have a bit of complexity in the implementation of the tool, so that we don't need to change the way we start/run jetty, nor add another mechanism that needs to be documented and maintained.
cheers
