Hello
We are currently facing a problem with the latest version of m2eclipse:
- Developer has a set of projects opened in eclipse, and they are in a
stable/compiled state. Project->"Build automatically" is enabled.
- He restarts eclipse.
- Sometimes (maybe in about 50 % of the cases) a full rebuild is
triggered. Even though there is no good reason for doing this.
This hurts, as some of these projects are quite large, and the developer
has to wait for about 5-15 minutes....
There is also the observation, that in such cases, a "compile" is done
twice, the first time it gets a lot of compile errors, as it seems that
the mavne-compile-classpath is NOT set in that situaiton. Developer then
typically cancel the build. In this situation, the next entry in
eclipse's "progress list" is typically the "update maven classpath
container", which then obviously corrects the classpath. The last one in
the progress list is then the java-compile, which then typically
suceeds.
Thinking a bit about the internals of this (without checking the code of
m2eclipse): Could it be that during startup of eclipse, tasks are
created, placed into the "progress/task list" and then executed, that we
depend on the right ordering of that steps, and that sometimes (based on
some bad timing or whatever), these entries are added in the wrong order
?.
PS: I've checked the ordering of the "Builders" in those projects:
"Maven Builder" is listed before the Java Builder.
Thanks for any help.
DI Gerhard Langs
ACT Software Development
SYSTEMA
Human Information Systems
Gesellschaft m.b.H.
Pachergasse 4
A-4400 Steyr
S \\ //// S T E M A
\\ //// E-Mail: mailto:[EMAIL PROTECTED]
\\ //// Phone: +43 (0)732 661008 40
//// Mobile: -
//// FAX: +43 (0)7252 587 300
//// WEB: http://www.systema.info <http://www.systema.info/>
Firmenbuchnummer FN 186491b, Landesgericht Steyr, Firmensitz: A-4400
Steyr, Pachergasse 4
