I generally like the idea, would this just be on the jetty7 trunk?
> jetty-util - left as is
>
> jetty - the core jetty server with handlers
> jetty-xml - XML configuration, may be used standalone, or if jetty.xml
> or webapps are used.
when you say standalone, are you meaning that it wouldn't require the
jetty or jetty-util modules in the classpath?
> jetty-servlet - the servlet handler and associated components
> jetty-webapp - the configure a webapp with web.xml
> jetty-ssl - the ssl connectors (moved out of the security package)
we could also do the ssl package addition as well to fix up that osgi
packaging issue as well..
Based on Jan's questions about the packaging of distros and whatnot on
another thread, we could easily build a jetty-embeddable artifact that
packages up the various required dependencies into a single jar and
publish that artifact into the repo, would be good because we could
scrape out the static files that are not required either, like the
maven directory with the pom.xml file inside it. Every K counts with
embedding and I think that would garner some goodwill from that
community :). I think we could also do this based on the existing
jetty buildout but it would have to be some managed includes and
excludes statements to get the right class files into the right
place...would be much easier to manage that with clearly delineated
artfacts.
jesse
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
--
jesse mcconnell
[hidden email]
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Locked
