I have a remote maven repo set up and can successfully upload artifacts and download via POMs. I also see the repo listed along with maven central in my m2eclipse global 'Maven Repositories'.
My problem is that while Maven Central is browsable and updatable in m2eclipse, my internal one is not and when it tries to update I get this:
"Unable to update index for Nexus|http://devserver:8081/nexus/content/groups/public"
Putting that url in a browser does work.
A solution is "I was able to fix it by launching the Nexus webapp and I choose repair index and rebuild index on the Public Repository Group."
but I can not rebuild the public index, and actually the index works fine for my colleague in the same office.
Any ideas how to make m2eclipse to index properly? Thanks!
Nexus Repository 3 does in fact support Maven (2) as a format.
The Rebuild Index button allows you to drop and recreate the search index for the proxy repository, synchronizing the contents with search index.
Introduction. Historically Nexus Repository Manager started as a repository manager supporting the Maven repository format and it continues to include excellent support for users of Apache Maven, Apache Ant/Ivy, Eclipse Aether, Gradle and others.
I had the same problem: it happens, i believe, when the local m2e index becomes corrupted, mainly when an Eclipse/VM crash occurs. I have found that, for my configuration, the index resides in .m2/repository/.cache/m2e
I closed Eclipse, deleted all the subfolders inside that folder, and I fixed the problem.
I'm sure that it suffice to seek the file(s) where lies the index, but deleting the whole directory worked fine for me.
Ensure, before deleting, that your remote maven repo index is not corrupt (right-click repair Index in the public repository of Nexus).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With