Thnx, Stefan for your reply.

Yes, we're using 0.0.12

I'm afraid that turning off "build automatically" is not really an option here. 
We are in a mirgration project *TO* maven, and there are some folks who just 
wait to see things like this, an I'm with all developers who see "build 
automatically" as being a central feature of eclipse.

Gerhard.


-----Ursprüngliche Nachricht-----
Von: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 6. März 2008 18:31
An: [email protected]
Betreff: Re: [m2eclipse-user] Unnecessary Rebuilds after Eclipse restart

Is your latest version 0.0.12?

We changed to have build automatically off and I applied the code from 
http://jira.codehaus.org/browse/MNGECLIPSE-432. That makes the plugin 
usable in these situations. If you need to build, you can do it manually 
(e.g. for debug or JUnit tests within Eclipse).

regards,

Stefan

Langs Gerhard wrote:
> 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
> 
>  
> 

-- 
best regards,

Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.    +49 (341) 9 60 50 07
fax.    +49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.    www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

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

    http://xircles.codehaus.org/manage_email



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

    http://xircles.codehaus.org/manage_email


Reply via email to