houzecl wrote:
I tried to do something clean. independant from previous Eclipse
installations and workspace. Therfeore here what I did:
installed eclipse-jee-europa-win32.zip (Version: 3.3.0 Build id:
I20070621-1340) in a new location
no additional plugin, and no plugin desactivated
created an empty workspace in a new location
installed maven integration for eclipse 0.0.11 (including mylyn stuff)
went to maven preferences:
it took a very long time to find my user settings.xml
What do you mean by that?
then, I made the Global settings point to my Maven 2.0.7 Installation
configuration settings
so far so good except that when i "apply" I have this unfriendly warning:
Unable to parse user settings file
(even if I take out the global settings, or if I restart eclipse).
This issue already been reported and it is fixed in trunk.
However, reindexing local repository did not crash :-) BUT I got a cryptic
warning:
While loading class
"org.apache.lucene.index.KeepOnlyLastCommitDeletionPolicy", thread
"Thread[Worker-3,5,main]" timed out waiting (5000ms) for thread
"Thread[main,6,main]" to finish starting bundle
"[EMAIL PROTECTED]/org.maven.ide.eclipse_0.0.11.20070916-2300/ [477]". To avoid
deadlock, thread "Thread[Worker-3,5,main]" is proceeding but
"org.apache.lucene.index.KeepOnlyLastCommitDeletionPolicy" may not be fully
initialized.
On startup plugin can trigger reindexing of the local repository and
it seems like it indexer job been started before plugin is initialized.
I've added some delay to workaround that. It will be available in the
next build.
then, I imported a multimodule project
No dependencies appear in buildpath
project did not compile, and I got this exception:
Let's take one thing at a time. Shall we. :-)
Please create jira issue for this and attach project that would allow
to reproduce this issue. We have some basic tests that cover multimodule
project import but new test case will be a huge help.
java.lang.NullPointerException
at
org.maven.ide.eclipse.container.Maven2Builder.addModulePoms(Maven2Builder.java:103)
at
org.maven.ide.eclipse.container.Maven2Builder.addModulePoms(Maven2Builder.java:110)
at
org.maven.ide.eclipse.container.Maven2Builder.build(Maven2Builder.java:80)
...
Therefore, I tried to use the screen you reference in your reply
I just unchecked: "resolve dependencies from workspace projects" (I dont
have any)
the other box was checked: "include dependencies and source folders from
modules"
I left it checked
I had a look ath the dependency tab: empty (probably because my multimodule
has no dependency and just sub-modules with their own dependencies ???)
because it is simply not implemented yet.
CONCLUSION:
I have some real difficulties understanding the differences between Maven
Enable ... submenu options when you are on the project, and the "dependency
resolver configuration" screen which is quite hard to get to.
I'll try to improve labels in the future versions. Currently they are
like this:
Enable Workspace Resolution == Resolve dependencies from workspace
projects
Enable Nested Modules == Include dependencies and source folders from
modules
Both those settings affect what dependencies are added to the "Maven
Dependencies" container. When "Workspace Resolution" is on, projects
from Eclipse Workspace will replace matching jars. When "Nested Modules"
is on, dependencies from nested modules will be also added to the "Maven
Dependencies" container (so you could use single project for all your
nested modules).
In addition, when "Nested Nodules" is on, "Update Source Folders"
action will also include source folders from nested modules, and when it
off, only source folders from the root project will be added.
and, it should not crash , even if the project has no workspace dependency.
I agree, but we need some test cases, so we could reproduce and fix
those crashes.
apart from that, it's promising. Thanks Eugene.
You are welcome. Thanks for the bug reports. Keep em' coming. :-)
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
