Re: Moving site plugin webapp to another plugin
+1 Milos On 1/11/07, Jason van Zyl [EMAIL PROTECTED] wrote: 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]
Re: Moving site plugin webapp to another plugin
Jason van Zyl wrote: 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. +1, it is as you say a bit of a surprise to downlown the J2EE stack to run javadoc or transform some APT :) -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
On 1/11/07, Trygve Laugstøl [EMAIL PROTECTED] wrote: Jason van Zyl wrote: 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. +1, it is as you say a bit of a surprise to downlown the J2EE stack to run javadoc or transform some APT :) Same here. +1 -- Trygve - 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]
Re: Moving site plugin webapp to another plugin
+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]
Re: Moving site plugin webapp to another plugin
-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]
Re: Moving site plugin webapp to another plugin
On 11/01/07, Kenney Westerhof [EMAIL PROTECTED] wrote: In short: why bother? :) I tend to agree with Kenney. Besides, all good developers have jetty in their local repo already ;) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
On 11 Jan 07, at 9:14 AM 11 Jan 07, Kenney Westerhof wrote:
-0
More plugins are bad IMHO.
I don't think so especially when it encourages a separation of
concerns. Publishing a site should not require a servlet container.
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
It's way more then that. It triggers pulling down the dependency
plugin, the ant run plugin. All its dependencies. From a clean
repository I've seen it take quite some time to pull everything down.
Jason.
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
On 11 Jan 07, at 9:20 AM 11 Jan 07, Mark Hobson wrote: Besides, all good developers have jetty in their local repo already ;) Yes, following that logic why don't we just stick all the plugins in one in one plugin and not bother trying to separate concerns at all. Then we'll only have one plugin and when people run mvn clean they will just get everything they need? I have watched bewildered users run mvn site and ask why all of god's green earth is being downloaded and it makes Maven unpleasant to use. Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
On 11/01/07, Jason van Zyl [EMAIL PROTECTED] wrote: Yes, following that logic why don't we just stick all the plugins in one in one plugin and not bother trying to separate concerns at all. Then we'll only have one plugin and when people run mvn clean they will just get everything they need? uberplugin.. sounds like a good candidate for mojo.codehaus :) I have watched bewildered users run mvn site and ask why all of god's green earth is being downloaded and it makes Maven unpleasant to use. Can't see it being much of a barrier for entry - I would have thought most Maven users would be used to seeing many seemingly random libraries being downloaded the first time they execute a new goal. The site:site and site:run goals are closely related and I would expect them to be provided by the same plugin. Maybe per-goal dependencies would be the way to go. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
+1 On 11 Jan 2007, at 04:49, Jason van Zyl wrote: 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]
Re: Moving site plugin webapp to another plugin
On 12/01/2007, at 1:14 AM, Kenney Westerhof wrote: I imagine most developers have at least a 2Mbit downlink You have quite an imagination :) I recently upgraded back up to a 1.5Mbit connection from 512Kbit. It's the highest I can get in my region, and usually is significantly more expensive. I expect there are developers in less prosperous places that don't have even that luxury. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving site plugin webapp to another plugin
[X] 0 - Don't care. This is one case where I'd like to be able to alias a goal to a new plugin, or dual-alias the goal prefix. I agree the webapp belongs in a different plugin, and probably should have started it that way, but I really prefer to use site:run. If it does get moved, and we can't do such aliasing, then I'd like site:run to be replaced with a call to invoke mvn site-runner:run or whatever it is, with a big deprecation message. I think I like Kenney's suggestion with an alternate name: turn the webapp bit into site:war (which requires no dependencies), and then use the jetty plugin to run it. - Brett On 11/01/2007, at 3:49 PM, Jason van Zyl wrote: 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]
Re: Moving site plugin webapp to another plugin
+1 I'd rather download only what I need. I have 512Kpbs (max). Other people here in Asia have slower connections because of the recent earthquake--fiber optic cables were cut if you haven't heard the news yet. On 1/12/07, Brett Porter [EMAIL PROTECTED] wrote: On 12/01/2007, at 1:14 AM, Kenney Westerhof wrote: I imagine most developers have at least a 2Mbit downlink You have quite an imagination :) I recently upgraded back up to a 1.5Mbit connection from 512Kbit. It's the highest I can get in my region, and usually is significantly more expensive. I expect there are developers in less prosperous places that don't have even that luxury. - Brett - 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]
Moving site plugin webapp to another plugin
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]
