I'm having difficulty in deciding at which point in this chain to reply :). So somewhat randomly I'll reply here!
On Sat, 2010-12-11 at 18:59 +0000, Marnie McCormack wrote: > Much as I hate to raise the subject - isn't this primarily a debate about > dependency management ? > > I have the same problems using IntelliJ. It was pretty much the onlt thing I > liked about the maven build -> generated project files ! > How about using the ant-eclipse generator, has anyone been using it ? > http://ant-eclipse.sourceforge.net/ As someone else said (Robbie I think) I'm not for checking in things that can be generated, so if I can get the eclipse files by generating them I'd be very happy. Note that this is exactly how we get (most of) the Visual Studio project files for the C++ code. > ... > > > > 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. I may have missed this built in antness in eclipse (or maybe I"m missing the correct plugin), but I couldn't get a single top level project imported from the top level build.xml to work. So I gave up on a single project and qua the wiki page am using a project per java module (I'm not building all of them just the broker and client and dependencies). > > > > > > Of course this is if you use a single eclipse project for all Qpid > > > java files (like I do) wheras if one wanted to create a project per- > > > module, you then need to manage the dependencies between modules > > > *MUCH* more carefully! > > > > My point was that's one of the reasons *why* I do it that (single project) > > way :) > > > > > > > > I'm still not sure which of these two mechanisms Andrew is using? As I said above one project per module. And I deliberately set out to find the minimum dependencies for what I'm building because my experience with nearly everything else is that minimising dependencies is always a good thing. Practically I did it so that I'd understand what all the many jar in lib were for - fortunately I didn't seem to need many of them. This is also because the work I'm doing will involve bringing in other code with its on dependencies and just dumping a truckload of new jars just seems wrong, so I want to understand what I'm doing here. > ... > > > > > > Well, my general feeling is that the difference between workflows in > > > Eclipse, based on the many possibilities provided by the range of > > > plugins and the mix of command line or IDE options, for various > > > things, mitigates checking in the '.project' and '.classpath' files. This could well be true and is why I asked in the first place, but the project files seem to be very simple to my eyes. > ... [not wishing to revisit a previously contentious discussion :-)] > > I'm not sure compatibility would be a problem, the files are pretty simple > > and don't seem to have changed for as long as I've ever looked inside them. > > Differences between developer preference is what will cause issues most I > > think. The project files I've got look trivially simple, so I doubt there's much compatibility issue - I'm using both 3.5 (or is it 3.4) and 3.6 and they both seem fine. > > > > Example project files could always be checked in to a directory in the > > tree, > > rather than into a location Eclipse would actually pick them up directly > > and > > use them. Of course, then they will simply become out date if no one kept > > them fresh, defeating the point. What I'd really prefer is if when you import a tree from git eclipse will correctly pick up the project files and get the projects. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
