Re: [jetty-dev] Jetty Plugin Functionality / Getting rid of Jetty Highti

[Thomas Becker <tbecker@xxxxxxxxxxx>]

The benefit of a separate directory for everything not coming from 
eclipse is that you can easily identify what's standard eclipse, 
install/remove the whole plugin, check what plugins are installed.
Plus a single additional config file like jetty-plugins.xml where you 
can activate/deactivate plugins.

On the other side I've to agree that we already have modularity and 
sticking to it makes good sense.

We need to decide how much we want to separate plugins from the rest.

On 11/4/11 12:20 AM, Greg Wilkins wrote:
> Thomas et al,
>
> I was thinking that in regards to configuration, we already have some
> modularity support in the form of:
>
>   lib/foo  - contains the jars and dependencies for foo module
>   etc/jetty-foo.xml - contains the configuration for foo module.
>
> So it would be good to see if a module system could use this pattern
> rather than add another one.
>
> I do see a need for a plugins directory, but mostly to contain meta
> data about the plugin and perhaps some example webapps and context xml
> files.
>
> The hardest thing for modules, is going to be the manipulation of
> start.ini, as it is this file that will ultimately control what
> modules are on the classpath and what configurations are executed.  I
> see we need a utility to maintain start.ini rather than encouraging
> manual editing.
>
> cheers
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

--
thomas becker
tbecker@xxxxxxxxxxx

http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)