Updating Classpath Container .... is very very slow

[chhe...@gmail.com]

I am in the process of migrating to Q from m2eclipse: generally i like
Q for Eclipse ;-)
But i came across a annoying problem:

The updating of the Classpath Container takes really long: up to 5
Minutes or more in my Configuration and thus "other" User actions - >
a real killer .......

Here a "Summary" of my Configuration Information:
Eclipse 3.3.x
java.version=1.6.0_03
Trunk Version of Q for Eclipse
Os : Window XP

What else?
The Lokal Repository is on a shared Drive.

What else?

Hopefully it is "just" a Configuration Issue.... but which?
Does anybody have an idea or has experienced simliar problems?

Christoph

[chhe...@gmail.com]

Maybe an important addition:

the local repository is on a shared remote Windows drive.
But i was using the same configuration for m2eclipse and there i
havn't found any problems in that direction.

[Abel Muiño Vizcaino]

It shouldn't take that long.

Some things you can try in Eclipse Preferences > Maven:

 - If you're downloading sources or javadocs, disable that option.

 - Put maven in off-line mode.

My guess is that you're using several SNAPSHOT dependencies and that maven is checking the remote repository.

If this was your first run, it might be downloading dependencies... to get more information, open the Maven Events view. You can set the Filter to debug to see every message Maven is providing (downloads, errors, whatever...). Note that this also will slow things a bit, so change the filters to "Info" level once you're done.

If this does not help you, please file n issue with an attached test case so we can reproduce the problem (that way we can determine if having the local repo in a shared drive is affecting performance... although there's little we can do in that case).

--

Abel Muiño Vizcaino - http://ramblingabout.wordpress.com

[Abel Muiño]

I'm CCing to the users mailing list. I didn't realize this was sent directly to me.

I was expecting more events displayed. By default, the maven events view filters out debug messages. You could try changing the filter to debug so you can see them (be aware that there can be a huge amount of data to display and can take some time, remember to switch back to info level to keep the usual performance).

If you have many SNAPSHOT projects, maven will try to connect to the remote repositories, which is slow. Have you tried to configure q4e to run in off-line mode (there's a checkbox in the Eclipse Preferences > Maven).
Also... have you compared performance with the maven command line tools? Try running maven process-test-resources on a single project (we can't be faster than maven).

Thanks for reporting!

On Jan 22, 2008 12:01 PM, tomiiik <tom...@gmail.com> wrote:

I appreciate your effort a lot, your kind of approach is great! - didn't
expect any answer :)

- 'm using the latest version from your development update site
- 'm running quite big amount of projects at a time ( 30-40 opened, <
100 total).
- The time consumed by the single project is approx. 1 minute.
- maven events occurred very rarely ( just one while I was enabling
projects to work with your plug-in correctly);
 but the first startup took over an half an hour.

carpe diem!


  tomas rohrbacher

Abel Muiño wrote:
> Thanks!
>
> Have you tried to display the maven events view and see what output is
> there?
>
> Also, it would be great to know:
>   - what q4e version you're running
>   - how many (q4e enabled) projects are on the workspace
>   - how long does it take
>
> If you're using an open source project, please tell us so we can
> download the sources and try to reproduce what you see.

--
  tomas rohrbacher
############   tomiiiq<at> gmail.com   <at> email
############   tomiq<at>njs.netlab.cz <at> jabber
####### ~~ #   tomiiiq                <at> skype
# o====\_/ #   161731513              <at> icq

--
Abel Muiño - http://ramblingabout.wordpress.com/

[tomiiik]

I started my eclipse workspace yesterday evening with 'work offline'
checked, I got asleep, woke up in the morning and it still continues
to "Update project dependencies". I wonder where is the issue.

I encounter some odd behavior when the same dependencies are looked up
again and again for any project ( e.g. many soap dependencies our
domain modules need are looked up even for controller modules
dependent on those domain modules)

I hope I could be able to master the dependency management code, but
can be anyone of u to help? ( documentation | diagrams?) My approach
is going to be somewhat different from the current one - the q4e
dependency management behavior seems a bit itchy to me.

[Carlos Sanchez]

seems that work offline didnt work
http://code.google.com/p/q4e/issues/detail?id=209

Now it's fixed for 0.5.0

--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride