|
»
« Return to Thread: too many jars? jetty-util jetty-io jetty-http ???
Re: too many jars? jetty-util jetty-io jetty-http ???
by janb
::
Rate this Message:
Greg,
[snip]
> I'd like to add a jetty-all.jar module on the eclipse
> project that will produce an aggregate bundle of all
> jetty@eclipse jars, currently:
>
> jetty-ajp
> jetty-annotations
> jetty-client
> jetty-continuation
> jetty-deploy
> jetty-http
> jetty-io
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
> jetty-security
> jetty-server
> jetty-servlet
> jetty-servlets
> jetty-util
> jetty-webapp
> jetty-xml
+1 to the jetty-all jar
> But I'm wondering if we have been a little to pure with the breakout
> of modules. Specifically, do we really need util, io and http to
> be separate?
>
> To that end, I have three proposals:
>
>
> a) merge io,http,continuation back into jetty-util and it
> will be slighly wrongly named as it will have classes from
> not just the util package.
>
> b) merge io,http,continuation and util into a jetty-common
> module.
>
> c) leave io,http,continuation separate, but have a jetty-common
> aggregation module that builds an combined jar.
>
>
> I like c) as advanced users could still directly depend on the
> smaller modules if they wanted (and exclude jetty-common.jar)
Merging them all back into one jar might not be possible - I thought
the main driver for separation was cyclic dependencies?
+1 for option c) to maintain separate jars but a convenience jar
with those combined. Not sure on the naming of this jar - see
below for more.
> The final question I have is on naming of aggregate jars.
> Ie do we want to differentiate aggregate jars from normal package
> jars? So for the common aggregate jar, I can see the following
> naming options:
>
> jetty-common-aggregate
> jetty-common-agg
> jetty-aggregate-common
> jetty-agg-common
> jetty-a-common
> jetty--common
>
>
> I like the last two because they will sort so that all aggregate
> modules are together. I know the -- is pretty arbitrary, but
> it is after all a convention that regardless of name will need
> to be backed up by documentation.
-1 on the -- naming convention. Too subtle and looks like a typo.
Maybe some systems won't parse that correctly either. "Common"
makes it sound like you have to have that _in addition_ to other
jars.
Perhaps jetty-xxx-all ?
jetty-util-all:
jetty-util
jetty-io
jetty-http
jetty-continuation
jetty-server-all:
jetty-util
jetty-io
jetty-http
jetty-continuation
jetty-server
jetty-security
jetty-servlet
jetty-xml
jetty-webapp
jetty-deploy
jetty-jmx
jetty-jaspi
jetty-jmx
jetty-jndi
jetty-plus
jetty-rewrite
jetty-client-all:
jetty-util
jetty-io
jetty-http
jetty-client
jetty-all:
jetty-ajp
jetty-annotations
jetty-client
jetty-continuation
jetty-deploy
jetty-http
jetty-io
jetty-jaspi
jetty-jmx
jetty-jndi
jetty-plus
jetty-rewrite
jetty-security
jetty-server
jetty-servlet
jetty-servlets
jetty-util
jetty-webapp
jetty-xml
Jan
>
>
> Regardless of the name, I can see us quickly doing the following
> aggregate jars:
>
> jetty--common-aggregate
> jetty-util
> jetty-io
> jetty-http
> jetty-continuation
>
> jetty--server
> jetty-util
> jetty-io
> jetty-http
> jetty-continuation
> jetty-server
> jetty-security
> jetty-servlet
> jetty-xml
> jetty-webapp
> jetty-deploy
> jetty-jmx
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
>
> jetty--client
> jetty-util
> jetty-io
> jetty-http
> jetty-client
>
> jetty--all
> jetty-ajp
> jetty-annotations
> jetty-client
> jetty-continuation
> jetty-deploy
> jetty-http
> jetty-io
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
> jetty-security
> jetty-server
> jetty-servlet
> jetty-servlets
> jetty-util
> jetty-webapp
> jetty-xml
>
>
>
> thoughts ?
>
>
>
> cheers
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@...
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
--
Jan Bartel, Webtide LLC | janb@... | http://www.webtide.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[snip]
> I'd like to add a jetty-all.jar module on the eclipse
> project that will produce an aggregate bundle of all
> jetty@eclipse jars, currently:
>
> jetty-ajp
> jetty-annotations
> jetty-client
> jetty-continuation
> jetty-deploy
> jetty-http
> jetty-io
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
> jetty-security
> jetty-server
> jetty-servlet
> jetty-servlets
> jetty-util
> jetty-webapp
> jetty-xml
+1 to the jetty-all jar
> But I'm wondering if we have been a little to pure with the breakout
> of modules. Specifically, do we really need util, io and http to
> be separate?
>
> To that end, I have three proposals:
>
>
> a) merge io,http,continuation back into jetty-util and it
> will be slighly wrongly named as it will have classes from
> not just the util package.
>
> b) merge io,http,continuation and util into a jetty-common
> module.
>
> c) leave io,http,continuation separate, but have a jetty-common
> aggregation module that builds an combined jar.
>
>
> I like c) as advanced users could still directly depend on the
> smaller modules if they wanted (and exclude jetty-common.jar)
Merging them all back into one jar might not be possible - I thought
the main driver for separation was cyclic dependencies?
+1 for option c) to maintain separate jars but a convenience jar
with those combined. Not sure on the naming of this jar - see
below for more.
> The final question I have is on naming of aggregate jars.
> Ie do we want to differentiate aggregate jars from normal package
> jars? So for the common aggregate jar, I can see the following
> naming options:
>
> jetty-common-aggregate
> jetty-common-agg
> jetty-aggregate-common
> jetty-agg-common
> jetty-a-common
> jetty--common
>
>
> I like the last two because they will sort so that all aggregate
> modules are together. I know the -- is pretty arbitrary, but
> it is after all a convention that regardless of name will need
> to be backed up by documentation.
-1 on the -- naming convention. Too subtle and looks like a typo.
Maybe some systems won't parse that correctly either. "Common"
makes it sound like you have to have that _in addition_ to other
jars.
Perhaps jetty-xxx-all ?
jetty-util-all:
jetty-util
jetty-io
jetty-http
jetty-continuation
jetty-server-all:
jetty-util
jetty-io
jetty-http
jetty-continuation
jetty-server
jetty-security
jetty-servlet
jetty-xml
jetty-webapp
jetty-deploy
jetty-jmx
jetty-jaspi
jetty-jmx
jetty-jndi
jetty-plus
jetty-rewrite
jetty-client-all:
jetty-util
jetty-io
jetty-http
jetty-client
jetty-all:
jetty-ajp
jetty-annotations
jetty-client
jetty-continuation
jetty-deploy
jetty-http
jetty-io
jetty-jaspi
jetty-jmx
jetty-jndi
jetty-plus
jetty-rewrite
jetty-security
jetty-server
jetty-servlet
jetty-servlets
jetty-util
jetty-webapp
jetty-xml
Jan
>
>
> Regardless of the name, I can see us quickly doing the following
> aggregate jars:
>
> jetty--common-aggregate
> jetty-util
> jetty-io
> jetty-http
> jetty-continuation
>
> jetty--server
> jetty-util
> jetty-io
> jetty-http
> jetty-continuation
> jetty-server
> jetty-security
> jetty-servlet
> jetty-xml
> jetty-webapp
> jetty-deploy
> jetty-jmx
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
>
> jetty--client
> jetty-util
> jetty-io
> jetty-http
> jetty-client
>
> jetty--all
> jetty-ajp
> jetty-annotations
> jetty-client
> jetty-continuation
> jetty-deploy
> jetty-http
> jetty-io
> jetty-jaspi
> jetty-jmx
> jetty-jndi
> jetty-plus
> jetty-rewrite
> jetty-security
> jetty-server
> jetty-servlet
> jetty-servlets
> jetty-util
> jetty-webapp
> jetty-xml
>
>
>
> thoughts ?
>
>
>
> cheers
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@...
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
--
Jan Bartel, Webtide LLC | janb@... | http://www.webtide.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: too many jars? jetty-util jetty-io jetty-http ???
| Free embeddable forum powered by Nabble | Forum Help |
