It sounds like you've done most of the modules. I'd like to start moving the code over to the proper place sometime later today - should I wait for your changes or just get going?
-- Jeremy [EMAIL PROTECTED] wrote: > Sebastien wrote: > >>I just looked again at the java/trunk/tools subproject and >>I don't think that we need to spend time and try to build it >>with Maven 2 now. >> >>This project drags more Eclipse dependencies (like startup.jar, >>which is probably not available in a Maven 2 repos) and a number >>of these dependencies will go away when we port this project to >>the SDO 2 runtime, which we're going to do very soon. I don't >>think that not being able to build the tools is blocking anybody >>right now, so I suggest we do the following: >>- hold off on trying to build tools with Maven 2 for now >>- port the tools to SDO 2, cleanup the dependencies >>- adjust the build then >> >>Now if you're already done and have the build of the tools working >>with Maven 2 then that's great! you can forget everything I just >>said :) > > > Heh heh... > > Well, I did get that module compiling, but dropped the dependency > on startup.jar in order to do it. I have not tried running it so > it's probably not working under m2 now. But I'll include the pom.xml > anyway as a starting point. >
