sverhagen wrote:
What version of m2eclipse you are using? Do you have local repository
manager or proxy configured in your environment (please show your
effective settings.xml)? Also, what indexes do you have declared in the
"Maven Indexes" view? You may want to invoke "Update Index" action for
"central" index in the "Maven Indexes" view.
Thanks. I may have entirely misunderstood this functionality. I supposed
these sources to be resolved through the normal dependency mechanism, but I
now realise that the repositories in question need to be added in Maven
Indexes.
It is actually bit more complicated and also somehow confusing. The
Maven dependency mechanism gets list of remote repositories for
downloading from the project's pom.xml and also taking parameters from
settings.xml.
In actions like "Open Type from Maven..." we don't really have
pom.xml, so we use repositories registered in the Maven Indexes view as
a base when downloading artifacts (we currently don't use settings.xml
to keep things simple, especially because profile activation could make
this stuff quite tricky).
On the other hand, all those spring artifacts you tried are available
in the Maven Central repository, which is registered in m2eclipse by
default and have index published. So, it should have worked out of the
box, unless you have some kind of proxy in the middle, or removed
Central index from the Maven Indexes view. That is why I asked you what
indexes you have declared in the Maven indexes view and if you have
proxy setup in your environment.
Now I appear to be finding sources (I see the proper icons), however,
Eclipse tells me it has some errors. Both a team member and I get "Error
opening the editor.". I also get "An internal error occurred during:
"Loading pom.xml". org.xml.sax.SAXParseException: Content is not allowed in
prolog." In the editor window itself I can get the details as pasted below.
In all my ignorance I would think: I wasn't opening a POM file to begin
with, was I? (I was opening a Java file.)
This is why I asked you what m2eclipse version you are using. There
was issue in m2eclipse 0.9.5 similar to what you describing and it been
fixed while ago in the 0.9.6 builds.
I do appreciate your enthusiasm and patience, though it would really
help you and the project if you'd answer questions before jumping into
your own conclusion.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
