Hi Jack,
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 :)
--
Jean-Sebastien
[EMAIL PROTECTED] wrote:
Just wanted to provide a quick update on the port to
maven2. I have most of the modules compiling via
maven2-style pom.xml files. I am seeing unit-test
failures that I am sure are due to details I have yet
to take care of, because the build under maven1 works
fine for me.
So, I'm looking at possibly Friday as the day I will
submit the patches. I do intend to test the Eclipse
project generation feature, once everything else is
working.
