hehe, well in my world NOTHING ever gets an 'mvn deploy' except from continuous integration... So I don't REALLY care HOW individual developers get their stuff working... All I care about is after they do an 'svn commit' I don't get an email telling me the build is broken! Frankly I don't even really care if they use Eclipse, lol. There is always someone that tries to be different, and after a few rounds of 'you broke the build because your checkstyle report says you don't format correctly', or they can't get whatever oddball toolset they wanted to use to work right, they always end up standardizing their build environement anyway. ;) Mainly because I won't help them fix anything that isn't the same as what I have, unless there's a darn good reason they HAD to use something different for task X. Our guys are pretty motivated, nobody wants to be the guy who's task estimates always come up short because he spent 3 days fooling with something that he could have just got the right setup for from /mnt/opt/development/...

Eugene Kuleshov wrote:

Now, tell me, why do I have to bother with exporting and telling everyone what need to be imported and how to import that if I can just put everything into version control? Unfortunately Maven can't help you with most of that and I don't really like the idea switching to command line after checking out code using IDE.

So far I haven't see any issues around different OS or Eclipse versions. Yes, some crappy plugins may screw things, but who want to use those crappy plugins?


Tod Harter wrote:
Too much pain and agony...

You can always export various settings etc, use a common set of templates etc. In a perfect world everyone could have the same setup, but with different developers on different versions of OS, and the fact that every variation of plugins and Eclipse versions has enough bugs to restrict it to only doing certain things it just isn't worth it. This is one reason for using Maven, you can at least enforce a consistent build environment from the command line everywhere.



---------------------------------------------------------------------
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