Eclipse maven updating indexes forever

If it is unable to retrieve this source artifact, you should ask the maintainers of the project in question to upload the appropriate Maven source bundle to the central Maven repository.

You can configure a project to resolve dependencies from a workspace.

It would be nice if you could just check timestamps instead of reloading the POM and keep the info necessary to track snapshots in some other location to avoid the whole long process.

Yeah, this is all public: On a related note, I'm often getting stuck in an endless "building workspace" step now which seems to be related to the maven plugin.

My hunch is that this is somehow related to me running maven on the command line as well. Do you have repeatable way to reproduce endless build?

Do you have your projects in public source repository that we can access? regards, Eugene --------------------------------------------------------------------- To unsubscribe from this list, please visit: Do you have repeatable way to reproduce endless build?Why is the m2e plugin always updating my dependencies all the time?Can you make it so it only does this if my POM is changed?The first option is by manually editing the file to add a dependency is that you must already know the information about the artifact, or use the features discussed in the next section to manually locate the artifact information in the repository indexes.The upside is that after manually adding the dependency and saving the , the project’s Maven Dependencies container will be automatically updated to include the new dependency.

Search for eclipse maven updating indexes forever:

eclipse maven updating indexes forever-55

I think I saw this problem couple of weeks ago but it went away after I ran "mvn clean package" from command line and refreshed from eclipse.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “eclipse maven updating indexes forever”