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

[Greg Wilkins <gregw@xxxxxxxxxxx>]

I understand the benefits of having a module contained in a single
directory, but I'm not sure that the benefits are worth the extra
complication.

The start.jar mechanism (while simple enough) already causes some
confusion because lib/foo/foo.jar  is not automatically put onto the
classpath, unless the OPTIONS=foo is included.     Having yet another
location to mix in modules, is only going to increase that confusion.

I'd really like the module utility to be about how a jetty is
assembled and not about how jetty runs.

I also don't see why remove is any harder with using the lib
directory.   Essentially the tool will have to do

   rm -fr lib/foo etc/jetty-foo.xml

instead of

  rm -fr plugins/foo

In either case, the tool doing the remove will need to update
start.ini to reflect the change.   I'm also kind of partial to having
meta data about all the files of a module, including a checksum - so
if you go to remove a module and the jetty-foo.xml file has been
modified, then you will get a warning about that and have to confirm
the deletion.


cheers