m2eclipse updates closed projects on startup?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

m2eclipse updates closed projects on startup?

Philip Reimer

Hello all,

I have a problem with my m2eclipse plugin, it seems. There are ~30
projects in my Eclipse workspace and most of them are closed (I only
open them if I need to work in them). However, m2eclipe seems to open
every last one of them during startup to update the dependencies or
something, even if the project is not a maven project. This slows down
the whole startup tremendously and if I try to do anything else before
the whole updating has finished it may happen that Eclipse totally
crashes and has to be killed and restarted.
My eclipse settings say that projects should be built automatically and
I turned off the Maven setting "Update Maven projects on startup". But
this setting seems to be ignored somehow?

Any hints would be appreciated. Thanks in advance.

This is happenin with Maven Integration for Eclipse version
0.10.0.20100209-0800 installed in Eclipse Galileo running on jdk 1.6 and
a Win XP Pro machine.

Best regards,
Philip

--

Dipl.-Wi.-Inf. Philip Reimer

[hidden email]

Telephone: +49-421-22092-59
Fax: +49-421-22092-10
Address: Institut für angewandte Systemtechnik Bremen GmbH
                Wiener Str. 1
                D-28359 Bremen




reimer.vcf (484 bytes) Download Attachment
signature.asc (267 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: m2eclipse updates closed projects on startup?

Philip Reimer
Am 31.05.2010 10:26, schrieb Philip Reimer:
>
> Hello all,

Hello once again,

this bug report seems to be related to my problem:
http://jira.codehaus.org/browse/MNGECLIPSE-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs



>
> I have a problem with my m2eclipse plugin, it seems. There are ~30
> projects in my Eclipse workspace and most of them are closed (I only
> open them if I need to work in them). However, m2eclipe seems to open
> every last one of them during startup to update the dependencies or
> something, even if the project is not a maven project. This slows down
> the whole startup tremendously and if I try to do anything else before
> the whole updating has finished it may happen that Eclipse totally
> crashes and has to be killed and restarted.
> My eclipse settings say that projects should be built automatically and
> I turned off the Maven setting "Update Maven projects on startup". But
> this setting seems to be ignored somehow?
>
> Any hints would be appreciated. Thanks in advance.
>
> This is happenin with Maven Integration for Eclipse version
> 0.10.0.20100209-0800 installed in Eclipse Galileo running on jdk 1.6 and
> a Win XP Pro machine.
>
> Best regards,
> Philip
>

--

Dipl.-Wi.-Inf. Philip Reimer

[hidden email]

Telephone: +49-421-22092-59
Fax: +49-421-22092-10
Address: Institut für angewandte Systemtechnik Bremen GmbH
                Wiener Str. 1
                D-28359 Bremen




reimer.vcf (484 bytes) Download Attachment
signature.asc (267 bytes) Download Attachment