On 1/5/10 AM, Lars Sonchocky-Helldorf wrote: the most annoying things are: - "Enabling/Disabling 1 maven 2 project" takes forever (more than 10 minutes!) and has no progress bar - first IAM build of a newly checked out project always fails when dependencies are missing (have to build at command line at first to fetch the dependencies) - "Updating classpath container" of a project takes forever (more than 10 minutes!Most importantly, the Maven plugin uses the import the dependencies of your dependencies.Fortunately, every step in the build process includes a “callback”, which is a hook where you can inject your own customizations.However, it is poorly-documented, and hasn’t been updated in forever (much like Ant! Also, the property scoping rules are very quirky, and it looks like I would have to create a completely separate Ant task just for the code within my loop.
On 1/12/10 AM, Lars Sonchocky-Helldorf wrote: you can open the Maven Events view and will display all the events, and you should see what is taking the time, but the progress bar should be working too, I don't know if there's a special case where we have a bug.With m2e, you can use Maven within Eclipse in a natural and intuitive interface. *Requires Eclipse Marketplace Client")Cannot complete the install because one or more required items could not be found.Software being installed: m2e - Maven Integration for Eclipse (includes Incubating components) 18.104.22.16840606-0033 (org.eclipse.m2e.feature.feature.group 22.214.171.12440606-0033) Missing requirement: Maven Integration for Eclipse 126.96.36.19940606-0033 (org.eclipse.m188.8.131.5240606-0033) requires 'bundle org.slf41.6.2' but it could not be found Cannot satisfy dependency: From: Maven POM XML Editor 184.108.40.20640606-0033 (org.eclipse.m2e.220.127.116.1140606-0033) To: bundle org.eclipse.m2[1.5.0,1.6.0) Cannot satisfy dependency: From: m2e - Maven Integration for Eclipse (includes Incubating components) 18.104.22.16840606-0033 (org.eclipse.m2e.feature.feature.group 22.214.171.12440606-0033) To: org.eclipse.m2e.[126.96.36.19940606-0033]Suddenly maven was disappeared all of my work spaces. I tried to recover by uninstalling and re installing m2e, but didn't work.They make no attempt to purge old dependencies that have been removed from the POM.The build script keeps your Eclipse projects up to date with most changes, but does not update classpath settings when dependencies change.You can use m2e to manage both simple and multi-module Maven projects, execute Maven builds via the Eclipse interface, and interact with Maven repositories.m2e makes development easier by integrating data from a project’s Object Model with Eclipse IDE features. *Requires Eclipse Marketplace Client](https://marketplace.eclipse.org/sites/all/themes/solstice/public/images/marketplace/btn-install.png)]( mpc_install=252 "Drag to your running Eclipse* workspace.I have been primarily living in the Maven world for some time now.I knew that ad-hoc scripting is a standard feature in more modern build systems, such as Gradle (Groovy), Buildr (JRuby), and sbt (Scala).query_format=advan ced ;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;b ug_status=REOPENED;product=IAM Why don't you work on those? Many minor/enhancement requests and nothing really critical, workarounds available.m2e provides comprehensive Maven integration for Eclipse.