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
