I see - the snapshots do present a tricky case. 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: http://admin.muleforge.org/projects/galaxy/repo 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. I'm wondering if it might have to do with me switching my project to use target/ instead of target-eclipse/. My hunch is that this is somehow related to me running maven on the command line as well. Thoughts? Dan On Wed, May 14, 2008 at 2:53 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Dan Diephouse wrote: > >> 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? I don't see any >> reason why it should have to load all my POMs and update dependencies when I >> restart, which is what it seems to be doing. >> > This is how it is intended to work. So, it only updates dependencies when > pom changes, but in order to track changes we need to load all Maven > projects when IDE starts. But reading projects may trigger updating > dependencies (especially snapshots), e.g. based on Maven's update rules. > Perhaps we could try to disable that and also track corner cases that may > trigger additional dependency resolution. > > Do you have your projects in public source repository that we can access? > It may help us to reproduce your issue. > > regards, > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Dan Diephouse http://mulesource.com | http://netzooid.com/blog
