1. Whether m2e can import a project "smoothly" currently largely depends
of set of maven plugins used by the project. You can control what maven
goals are executed on project import, update project configuration and
during the build. This works for some projects but is not a universal
solution. We plan major improvements in this area in 0.9.8 and 0.9.9.
2. m2e may be forcing update snapshot dependencies in some cases. I am
not 100% sure but I vaguely remember we discussed doing this.
Eugene, do you remember if offline mode is respected by all operations?
3. External Maven runtime is only used by Maven launch (i.e. Run
As->Maven). All other operations, like project import and update
dependencies, are using embedded version of maven. This particular error
message is a result of incompatibility between enforcer plugin and
rather old version of embedder if I am not mistaken. We plan to include
new embedder in 0.9.8.
--
Regards,
Igor
Walter Harley wrote:
I'm running Maven 2.0.9 and Eclipse 3.4.2 with M2Eclipse 0.9.7.200902090938
on Mac OS X.
In M2Eclipse I have prefs set to use external Maven, I have "offline"
checked, and I do NOT have "update Maven projects at startup" checked.
Earlier this afternoon, I sync'ed and successfully "mvn install"-ed a
certain project, we'll call it projectX, at the command line. Just now, I
imported the 'exam' project into Eclipse. (I did not update anything, and
only about three hours had passed.)
As soon as I imported the project, it spent the next 2.5 minutes downloading
updates; e.g., output like the following in the Eclipse console:
...
3/3/09 4:43:14 PM PST: [INFO] snapshot (some-module):1.3.0-SNAPSHOT:
checking for updates from java.net
...
3/3/09 4:43:33 PM PST: Downloading (my-company)-repository :
(another-module)-1.2.0-SNAPSHOT.jar
Then it failed, with the following error in the error log and console:
3/3/09 4:45:49 PM PST: Build errors for projectX;
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or missing
parameters: [Mojo parameter [name: 'rules'; alias: 'null']] for mojo:
org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce
So my questions are:
1. Does anyone else have this sort of thing working smoothly, i.e.,
importing Maven projects into Eclipse workspaces without errors, long
delays, and redundant downloads? If so, can you let me know what your
configuration is?
2. What does "offline" actually mean? I thought it would mean "don't
download things you already have in the repository" but
3. Why does it fail to build from inside Eclipse, when it worked at the
command line and I have Eclipse set to use the command-line version of
Maven? What does this particular error signify?
Thanks!
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
