FYI, created: http://jira.codehaus.org/browse/MNGECLIPSE-480 on my problem.
If someone knows, pls give me hints on which classes of m2eclipse to start investigations, on what's going on right after eclipse-start. And if my assumption (see link) is true. Maybe then I'm able to help on a fix - but unfortunately I have only limited knowledge on the inner things of eclipse (and m2eclipse) ----- Short continuation on off-topic: ----- We're quite late in our migration phase to maven, so we try to clean up remaining nasty topics - as this one. So, I dont want to touch our setup too much. As said, we do have some larger eclipse-projects, where opening projects, changing dependencies etc hurts. People somehow learn to live with it (keep modules opned etc), also the "Resolver Configuration" on the "Maven Dependencies" of an eclipse-project can reduce times - havent tried this, however). MNGECLIPSE-480 is a thing, which sometimes can not be prevented and is non-deterministic, (e.g. because of computer downtimes etc) One reason for using "build automatically": Eclipse *always* keeps me informed about the state of my source, and not only on request. Especially valuable in refactoring-situations. Don't get me wrong on this: If possible, I would like to have the problem fixed (btw, Eugene and others, thanks a lot for your work on m2eclipse), and dont want to reduce the efficiency of our developer's work by not using an eclipse feature, or by forcing them to follow one more guideline (like to turn of rebuilds before exiting eclipse). Have a nice weekend, Gerhard. -----Ursprüngliche Nachricht----- Von: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 7. März 2008 10:50 An: [email protected] Betreff: Re: AW: [m2eclipse-user] Unnecessary Rebuilds after Eclipse restart Hi Gerhard, I'm afraid that if you have skeptics about maven then using the m2eclipse plugin is not at all good for evangelizing. The problems sometimes outnumber the advantages, that's why I took a week or so to fix the worst problems in it myself. Maybe you should have a look at mvn eclipse:eclipse? Although off-topic, a word on automatic builds - why exaclty do you not want to switch it off? Eclipse will still do all the useful stuff, like code completion, refactorings, jump-to-source etc. The only advantage I see is if you depend on the classes built by eclipse, but you can change that to depend on the classes built by maven, and maybe if you run your JUnit tests from within Eclipse quite often. It also helps you to think in terms of maven, not in terms of eclipse, because then you will mostly use maven to verify that your package (artifact) can be built correctly, which is often different from eclipse. It is also noteworthy that if you have a multi-module project within one eclipse project, M2Eclipse will rebuild the whole project if you change a single pom.xml. There is an option to split those into single eclipse projects (one per module) but if there are (like we have) > 120 modules, this is really not an option. regards, Stefan Langs Gerhard wrote: > 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 >> >> >> > --------------------------------------------------------------------- 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
