Re: Reorg of the source hierarchy and precise version identification

Hello all, I've been busy this afternoon doing some housecleaning in the code base: - seperate folders for src/main - core java src/test - unit tests src/test-cactus - integration tests I've been building against the latests stable jars I could find, including hibernate 3.0.1 for which I had to change a lot of imports and some stuff in the configuration files. I just commited the version numbered jars because we are going to be playing with Maven 2 tomorrow night at the OSSGTP and I figured it might be easier to write the dependencies that way. I also ported the RSS macro to Rome 0.6 because it broke on the latest commons-digester. Rome sure is a sweet API ! We're going to be doing some other interesting things with Rome. So all of this stuff is still on my machine while I continue unit tests (actually these are quite long because a lot of them are actually integration tests and bring up hibernate (with showSql = true :( ) etc...), but since cruise control is coming back up, I'm going to just make sure the build runs and ant release works. I've been working on tests for my lifeblog stuff, and I definitely like running them one at a time directly in eclipse, even the server tests through Jetty. So I have to see how to refactor that so the other tests benefit and for it all to be ant and ide compatible. I bet you have a lot of ideas on that one Vincent ! ;) My concern, is what to do about your diffs and how changes to the src hierarchy could affect your current work. I hope that doesn't cause you too much pain. Please let me know if you have any ideas on this issue because I'm a bit stumped. Actually maybe I can just tell you when I start to commit and when its done and then you can move your sources in the right place (easy to do) and update. Cheers, -- Luis Arias http://www.xwiki.com http://www.innover-entreprendre.net +33 6 14 20 87 93 mobile