> -----Original Message----- > From: Andrew Stitcher [mailto:[email protected]] > Sent: 10 December 2010 19:29
<snip> > It looks like many java developers just include absolutely everything > they might need on the classpath, but I wanted to know what was going > on > and carefully added only what was necessary (to the extent I understand > what's going on!) for the projects I'm building. > I can't speak for anyone else, but that's exactly what I do for a variety of reasons, such as: a) it takes about 15 seconds to get set up in Eclipse, and you can use the main build files just as if you were using ant from the command line. b) I usually have several projects defined tracking different versions/checkouts of the codebase, again having a single one per version is a lot easier than messing around with say 15 module projects for each. c) The inter-module dependencies are fairly simple to keep track of yourself [admittedly, only once you know them in the first place], the build system enforces them already, and I find it's usually best/easiest to just run things from qpid/java rather than doing a specific sub module given that so many do have dependencies. d) Eclipse caches the status of files on disk and often needs its projects refreshed to ensure it is actually showing/using the current version and not a cached build, e.g. after you do a rebase; it's quicker just needing to worry about refreshing 1 project. e) I use Git to pull the rug out from under Eclipse and work on a variety of branches with the same project definition. The above means that having 1 project again makes life easier. f) I tend to keep my Eclipse project data separate from the repo checkouts, with my projects 'using existing source' out of the workspace tree, as I tend to mainly use the build at the cmd line. It also lets you forget about eclipse generated content without having to specifically ignore it, and gives you more freedom to do weirder things like having multiple projects pointing at the same set of source on disk (which you can't do anywhere near as easily if the source is in your Eclipse Workspace, without effort to trick Eclipse anyway). I'm sure there are more reasons I switched to doing it this way, but those are the main ones I can think of now. > > > > > Should I register this as an objection to checking in the eclipse > > > project files? > > > > > > > I wouldn't bother personally and won't be using them, but it's not an > objection as such. > > Ok, my major reason for wanting to do this is to share the project > files > over the several development machines I use, is there some better way > of > doing that? > > Andrew > In the past, when I first set things up and did it like you are trying now, I just emailed them to myself in all honesty :) Following that I used my own Git repos to shuffle things between machines, although that included source changes too as it was before I had commit rights. The way I define the projects now, I honestly find it's so easy to get set up that I don't feel the need to share them; it would take as long to reuse the definitions as it does to set them up in the first place, and I actually don't tend to work on the same things on different boxes now so I usually have different setups on them now anyway. Robbie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
