We are working with Maven core team to improve performance of the dependency resolution as well as few other things that would make Maven work better inside Eclipse.

Though I have few comments on initial performance comparison between Maven CLI and m2eclipse.

First of all it been unclear what time is actually been compared and to make fair comparison it should been a clean project in both cases (perhaps even with automatic builds turned off in the IDE). Another point to note is that when building in Eclipse, "Project / Clean" action is flushing dependency information, so it will not only recompile given project, but will update projects that may depend on the cleaned one. That obviously won't be the case in CLI and it is really hard to do the fair comparison in such conditions. To address the resolution issues, we will split dependency resolution out of the JDT build, so in our prototype it has smaller impact on the build time and also made workspace resolution more robust.

 Hope that helps.

 Eugene


Kees van Dieren wrote:
Same thing here. It was better with m2eclipse 0.10, but this has some other major issues.

Things to improve on 0.12 imo (applicable for a multimodule maven setup):
* snapshots are always checked for updates, even when <snapshotPolicy>never</snapshotPolicy> is added to all repositories * when cleaning all projects, for each projects, all dependenat project poms are read / parsed analyzed. In Progress view it says: updating (projectname): reading (projectname)/pom.xml. This takes about 0.75s per pom.xml. I think it should cache this, so that on a refresh/ clean this delay happens only once per dependency-project


On Feb 4, 2008 2:15 PM, VUB Stefan Seidel <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi,

    I also suspect that the m2 version embedded in the plugin has a
    different strategy for resolving artifacts. I struggled to create
    a test
    project but I was not able to find the cause. Here, we overwrite the
    central repository to point to a local proxy, but in Eclipse, maven
    tries to resolve artifacts from completely different repos (like
    apache-snapshots etc.). I don't know why, and the 2.0.8 never does
    that.

    regards,

    Stefan

    <mailto:[EMAIL PROTECTED]>



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to