Nigel,
Some of those issues are rooted in the Maven code and we expect them
to go away once we pickup the new Maven embedder (still waiting on the
Maven team for the release).
Right now we don't provide option to disable the Maven builder, but it
been discussed before. Though it worth to mention that plain dependency
management won't be sufficient if Maven project is using resource
filtering and some plugins that could generate code and resources from
other project files. Though we could take some shortcuts if project is
not using resource filtering and those generation plugins.
It might be confusing, but there are two separate settings:
* goals to run on project import and update project configuration (those
are needed to obtain the actual list of source folders, because some
Maven plugins can add repource and source folders to the project during
the build, e.g. modello, xmlbeans, jaxb, xdoclet, etc)
http://docs.codehaus.org/display/M2ECLIPSE/Maven+Settings
* goals to invoke on project clean and on resource changes (those are
used by the Maven builder)
http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management
For the latter there is no workspace defaults and those settings are
configured per-project. I suppose we could add global settings for that
and if you are interested in such feature, please submit an enhancement
request to the project issue tracker at
http://jira.codehaus.org/browse/MNGECLIPSE
To track downloading issue, please check what repository location and
what Maven's settings.xml are shown at Window / Preferences / Maven /
Installations and verify that it match your ~/.m2/repository
In regards to "offline", can you please clarify what you meant by "in
maven settings, turn on offline"
In regards to "process-test-resources" vs. "process-resource", can you
please clarify what you meant by "specified in the maven settings".
Please note that Eclipse may chose to run full build when you turn
"build automatically" on and there is a separate goal for that.
regards,
Eugene
Nigel Magnay wrote:
I'm sure I've had m2eclipse running before without such big problems,
so I'm wondering if something has changed.
Eclipse 3.4, m2eclipse 0.9.7.200810211352. Fast machine with local
nexus mirror configured in settings.xml.
This is a relatively large project - ~100 projects, ~80 artifacts.
From the commandline, an 'm2 install' will take about 22mins (but that
includes a full web-based integration test).
Before starting, the project has been locally built, so there is both
completed artifacts, and a fully populated ~/.m2/repository.
Start eclipse with a fresh workspace. Turn off Auto-build projects. In
maven settings, turn on offline, and turn off download repository
index updates.
Import maven projects - select top level, turn off a few of the found
projects (they seem to confuse m2eclipse and they're not useful.
Select [groupId].[artifactId] as name.
Status begins on 'Importing Maven projects'. This takes around 12
minutes, during which time in the log there seems to be a huge amount
of downloading going on:
11/25/08 10:42:47 AM GMT: [INFO] Using mirror: mirror.central for
repository: central
(mirror url: http://localhost:8081/nexus/content/repositories/central)
11/25/08 10:42:50 AM GMT: Downloading mirror.central :
org/codehaus/cargo/cargo-core-api/1.0-beta-1/cargo-core-api-1.0-beta-1.pom
11/25/08 10:42:50 AM GMT: Downloaded [mirror.central] ->
http://localhost:8081/nexus/content/repositories/central/org/codehaus/cargo/cargo-core-api/1.0-beta-1/cargo-core-api-1.0-beta-1.pom
Which is puzzling. I ought to be offline...
Once that finishes, there's a full 15 minutes of "Updating Maven
Dependencies". This seems to be really slow; and amongst the
reasonable 'setting source compatbility' output features, there's
swathes of
repeated
11/25/08 10:52:26 AM GMT: [WARN] While downloading javax.servlet:servlet-api:2.3
This artifact has been relocated to javax.servlet:servlet-api:2.3.
?! Why is it downloading that when updating dependencies? It's in the
local repository, it's not a snapshot..
Finally, when turning on 'Build automatically', there's a further 8
minutes of maven processing, doing [process-test-resources]. This
seems strange, I'd expect it to be process-resources as specified in
the maven settings.
So, in total it took about 35 minutes on an otherwise quiescent system
to get to the point of being able to cut code - any change in the
dependency ordering and I seem to be off on another 20 minute
roundtrip whilst it all happens again.
I assume it's something odd or broken in my pom files? There seems to
be masses of downloading activity (heaven help if there were no local
nexus!) which just looks wrong. All I really want out of it is the
dependency management - m2 is way too slow for a development
environment to be building things..
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
