-0
More plugins are bad IMHO. We could either remove that functionality
and just let people site:state jetty:run '-Dwar=${site.directory}'
or, in the future, make those deps scoped optional and specify
which ones are used for what mojo so that when you run that mojo
they won't be optional anymore.
jetty: 452kb
servlet-api: 139kb
jetty-util: 66kb
---------------------
0.6 MB
doxia-site-renderer: 32kb
doxia-core: 208kb
oro: 65kb
plexus-velocity: 8kb
velocity: 388kb
velocity-dep: 694kb
doxia-decoration-model: 41kb
------------------------------
1.4 MB
so removing jetty will only remove 30% from the deps needed specifically
for the site plugin. I imagine most developers have at least a 2Mbit
downlink, so this would reduce their build time 3 seconds, only once
(for me and all people with an intranet proxy it would decrease the build
time by about 60 milliseconds).
I think this is nothing compared to the size of all of maven's plugins
and dependencies (50+ MB or so?).
In short: why bother? :)
-- Kenney
Emmanuel Venisse wrote:
+1
Emmanuel
Jason van Zyl a écrit :
Can we put the webapp stuff that's currently in the site plugin in
another plugin so that when you simply want to generate your site you
don't drag down Jetty and all its dependencies? It really is something
unexpected and isn't something most would associate with just
generating a site. The functionality is cool, I just think it belong
in another plugin.
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]