Re: How to start with JAVA on I-series

Carl skrev den 02-11-2007 19:10

I definitely agree, but I would add that the benefits of having a
separate build process vary greatly depending on the size of the
project and development team.

For those smaller projects I have to work on alone where I develop e.g. using MyEclipse there is no easy way to export the war-deployment to a script.

Even so, one of the benefits underlying the "use a separate build process" is the ability to get up and running from scratch (i.e. removing the machine configuration from the set of parameters you must take in consideration when troubleshooting customer problems) and just by not allowing external jar-files (must be in a project) and absolute paths in launch projects (use variables) you can get 99% of the way. Then "Team projects" are just perfect - you create the file and send it to the new user, and then they extract all the necessary projects and files from your version control system.

Odd, that right before catching up on this thread I just finished
reading this article:
http://www.codinghorror.com/blog/archives/000988.html
Which is remarkably appropriate. The link to the email exchange in the
first article should invoke laughter or much sadness, depending on
your previous team experiences. Either way, it's worth a read if you
haven't already.

Just had the pleasure of entering such a project. Introduced "Team Projects" in Eclipse to the lone wolf developer which he immediately saw the value in. So after a bit of cleaning up of external jars and deployment descriptors we could work together well.

By the way, I don't agree fully that the F5-key is not a build process IF anyone can do it after loading up the workspace (which should only involve clicking ONE Ok-button). It is not perfect but it is _reproducible_.

Thanks for the link - good to show others in case it happens again :)