"Updating Maven Dependencies"

[Dan Diephouse-2]

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.

Dan

--
Dan Diephouse
http://mulesource.com | http://netzooid.com/blog

[Eugene Kuleshov]

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-2]

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 <eu@...> 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

[Igor Fedorenko-4]

Dan Diephouse wrote:

>
> 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?
>

Do you have repeatable way to reproduce endless build? 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.

--
Regards,
Igor

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Dan Diephouse-2]

Not yet unfortunately. I'll let you know if I find anything.

On Wed, May 14, 2008 at 4:35 PM, Igor Fedorenko <igor@...> wrote:

Dan Diephouse wrote:

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?

Do you have repeatable way to reproduce endless build? 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.

--
Regards,
Igor

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email

--
Dan Diephouse
http://mulesource.com | http://netzooid.com/blog

[Hasan Ceylan]

I think I have a clue on this issue...
Although I did not have so much tpme to dig it in, if m2eclipse and subversion is used together in the same work space then startup initialization ends up with deadlocks, both trying to acquire  semaphores.

I have a workspace with three level depth,
projects are *not* flat
top project has the team nature
projects are imported using import maven projects...

Regards,
Hasan Ceylan

Dan Diephouse-2 wrote:

Not yet unfortunately. I'll let you know if I find anything.

On Wed, May 14, 2008 at 4:35 PM, Igor Fedorenko <[e-mail]> wrote:

> Dan Diephouse wrote:
>
>
>> 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?
>>
>>
> Do you have repeatable way to reproduce endless build? 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.
>
> --
> Regards,
> Igor
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>


--
Dan Diephouse
http://mulesource.com | http://netzooid.com/blog

[Hasan Ceylan]

By the way,

This, I've seen with 20080603 and 20080627 m2eclipse versions and suversion 1.2.x and 1.4.x update site versions...

Hasan Ceylan


I think I have a clue on this issue...
Although I did not have so much tpme to dig it in, if m2eclipse and subversion is used together in the same work space then startup initialization ends up with deadlocks, both trying to acquire  semaphores.

I have a workspace with three level depth,
projects are *not* flat
top project has the team nature
projects are imported using import maven projects...

Regards,
Hasan Ceylan

Dan Diephouse-2 wrote:

Not yet unfortunately. I'll let you know if I find anything.

On Wed, May 14, 2008 at 4:35 PM, Igor Fedorenko <[e-mail]> wrote:

> Dan Diephouse wrote:
>
>
>> 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?
>>
>>
> Do you have repeatable way to reproduce endless build? 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.
>
> --
> Regards,
> Igor
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>


--
Dan Diephouse
http://mulesource.com | http://netzooid.com/blog

[Eugene Kuleshov]

Hasan Ceylan wrote:

> I think I have a clue on this issue...
> Although I did not have so much tpme to dig it in, if m2eclipse and
> subversion is used together in the same work space then startup
> initialization ends up with deadlocks, both trying to acquire  semaphores.
>
> I have a workspace with three level depth,
> projects are *not* flat
> top project has the team nature
> projects are imported using import maven projects...
>  

  Hasan, are you using Subclipse 1.2? If so, please read note in
installation reqs page [1] or better update to Subclipse 1.4

  If you see this with Subclipse 1.4, can you take a thread dump of
Eclipse JVM process [2] and send it to us.

  Thanks

  Eugene

[1]
http://docs.codehaus.org/display/M2ECLIPSE/Installation+Requirements#InstallationRequirements-InstallSubclipse
[2]
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-Howtogenerateathreaddump



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email