RE: [dbunit-developer] More updates to Maven build. Are we ready to switch to Maven?

[Eric P. <ep...@up...>]

Hi all,

I tried running org.dbunit.AllTests, and I do have one failure.  I submitted
it as bug:787899.  However, i realize that this may just be the one that
Manuel said would fail.  Manuel, can you verify this?

Eric Pugh

-----Original Message-----
From: dbu...@li...
[mailto:dbu...@li...]On Behalf Of Manuel
Laflamme
Sent: Wednesday, August 13, 2003 3:46 AM
To: dbu...@li...
Subject: RE: [dbunit-developer] More updates to Maven build. Are we
ready to switch to Maven?


> Manual, and folks..
>
> I updated the Maven project.xml, and also committed a bunch of
> import fixes
> and unused variable fixes suggested by PMD.  You can see the updated Maven
> style documentation here: http://www.dbunit.org/maven.  Additionally, MOST
> of the unit tests work (98.05%)!  However, I would love someone to run the
> unit tests against MSSQL and DB2 etc...

You need to run tests from the org.dbunit.AllTests suite. There are tests
that are skipped from some AllTests classes when features are not supported
by particular a database vendor. So if maven is running all existing tests
some of them will fail. BTW, there is one Ant test that is currently failing
with Hypersonic so you will not be able to get a 100%.

> To complete the conversion to Maven, these are the outstanding things:
> 1) A firm commitment that based on what people have seen, we want to use
> Maven.  If Manuel says "maven is our build tool" then that is good enough
> for me.  Basically, I don't want to spend a lot of time
> converting docs and
> debugging unit tests if we aren't going to go for it.

Yes I would like to use Maven as the build tool for the next major release
with the possibility of using it as the official website front end before
that (see #4).

> 3) Do we want to just port the existing documentation to the xdoc
> format, or
> does someone want to go through and edit them?  I can port the docs okay,
> but it might be a good idea to edit them with an eye to all the changes in
> DbUnit.

I think we should start by converting the existing html doc to xdoc. The
documentation defenetively need to be edited before the next major release
to include the new features and to correct current doc deficiencies.

> 4) Either decide to keep putting maven docs in the /maven dir, and update
> the homepage with a link, or just go and update the root to be the maven
> docs.

If we have a fully functional Maven build, then I vote for using the
official website front end before the next major release. Maven will not be
part of another 1.5.x minor release though to save us the work of merging
Maven stuff in "branch-1-5". I believe we will need to release a fix for bug
#786543 introduced in version 1.5.5.

> Any other issues people can think of?  I would like to finish the
> process of
> moving to maven based builds sooner versus later!

I believe that we should disable the Checkstyle report, as the DbUnit coding
standard does not match with the Maven one.

> Eric Pugh
>

Manuel




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
dbunit-developer mailing list
dbu...@li...
https://lists.sourceforge.net/lists/listinfo/dbunit-developer