You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by Jérôme Charron <je...@gmail.com> on 2006/03/03 01:06:14 UTC
Re: svn commit: r378655 - in /lucene/nutch/trunk/src/plugin: ./ analysis-de/ analysis-fr/ clustering-carrot2/ creativecommons/ index-basic/ index-more/ languageidentifier/ lib-commons-httpclient/ lib-http/ lib-jakarta-poi/ lib-log4j/ lib-lucene-analy
> Calling "compile-core" for every plugin makes builds really slow.
I was surprised that nobody complain about this... ;-)
> I
> think it's safe to assume that the core has already been compiled before
> plugins are compiled. Don't you?
It just ensure that the last modified core version is automatically compiled
while compiling a single plugin.
>From my point of view the time for a whole build is not a problem.
If I just work on core, then I can use the "fast" compile-core target.
And if I just work on a plugin, I only compile the plugin.
Finally I use the global compilation very rarely.
But perhaps that's not your case, and so it makes sense to reduce time of
the whole build.
Jérôme
Re: svn commit: r378655 - in /lucene/nutch/trunk/src/plugin: ./ analysis-de/ analysis-fr/ clustering-carrot2/ creativecommons/ index-basic/ index-more/ languageidentifier/ lib-commons-httpclient/ lib-http/ lib-jakarta-poi/ lib-log4j/ lib-lucene-analy
Posted by Jérôme Charron <je...@gmail.com>.
On 3/3/06, Doug Cutting <cu...@apache.org> wrote:
>
> Jérôme Charron wrote:
> > Here is my proposal. For each plugin:
> > * Define a target containing core (will be used when building single
> plugin)
> > * Define a target not containing core (will be used when building whole
> > code)
> > I commit this as soon as possible.
>
> That sounds perfect. Thanks!
Committed.
Quick benchs:
* Before : around 70s
* After : around 50s
Better, but not so perfect... :-(
Jérôme
Re: svn commit: r378655 - in /lucene/nutch/trunk/src/plugin: ./ analysis-de/
analysis-fr/ clustering-carrot2/ creativecommons/ index-basic/ index-more/
languageidentifier/ lib-commons-httpclient/ lib-http/ lib-jakarta-poi/ lib-log4j/
lib-lucene-analy
Posted by Doug Cutting <cu...@apache.org>.
Jérôme Charron wrote:
> Here is my proposal. For each plugin:
> * Define a target containing core (will be used when building single plugin)
> * Define a target not containing core (will be used when building whole
> code)
> I commit this as soon as possible.
That sounds perfect. Thanks!
Doug
Re: svn commit: r378655 - in /lucene/nutch/trunk/src/plugin: ./ analysis-de/ analysis-fr/ clustering-carrot2/ creativecommons/ index-basic/ index-more/ languageidentifier/ lib-commons-httpclient/ lib-http/ lib-jakarta-poi/ lib-log4j/ lib-lucene-analy
Posted by Jérôme Charron <je...@gmail.com>.
> In a distributed configuration one needs to rebuild the job jar each
> time anything changes, and hence must check all plugins, etc. So I
> would appreciate it if this didn't take quite so long.
Make sense!
Here is my proposal. For each plugin:
* Define a target containing core (will be used when building single plugin)
* Define a target not containing core (will be used when building whole
code)
I commit this as soon as possible.
Jérôme
--
http://motrech.free.fr/
http://www.frutch.org/
Re: svn commit: r378655 - in /lucene/nutch/trunk/src/plugin: ./ analysis-de/
analysis-fr/ clustering-carrot2/ creativecommons/ index-basic/ index-more/
languageidentifier/ lib-commons-httpclient/ lib-http/ lib-jakarta-poi/ lib-log4j/
lib-lucene-analy
Posted by Doug Cutting <cu...@apache.org>.
Jérôme Charron wrote:
> It just ensure that the last modified core version is automatically compiled
> while compiling a single plugin.
> From my point of view the time for a whole build is not a problem.
> If I just work on core, then I can use the "fast" compile-core target.
> And if I just work on a plugin, I only compile the plugin.
> Finally I use the global compilation very rarely.
> But perhaps that's not your case, and so it makes sense to reduce time of
> the whole build.
In a distributed configuration one needs to rebuild the job jar each
time anything changes, and hence must check all plugins, etc. So I
would appreciate it if this didn't take quite so long.
Doug