Jin James Wan wrote: > > When determined to port dbunit months ago, it's latest version is 2.3.0, > all the processes are work with this version, like OSR. I'm not sure if > we can change the version during the porting process. Or just we can > upgrade it after this version putback.
Ask Jim Walker I think he knows about that sort of thing. I do seem to remember someone else asking about that on sfwnv-discuss a few weeks back, so you could search for the reply to that (from whoever). But it seem silly putting an old version in (and all the bugs fixed in the later version) when it has moved on quite a bit since then (2.3.0 to 2.4.4). Paul > > Paul Cunningham wrote: >> Why is the version not 2.4.4 (the latest) anyway ? ... >> Quote: "2009-02-24 We are proud to announce the 2.4.4 release >> has been cut." >> >> Paul >> >> Amanda Waite wrote: >>> >>> Can you find a way to use the original source bundle from sourceforge >>> (dbunit-2.3.0-prj.tar.gz)? I'm not comfortable with you using a >>> custom source bundle. >>> >>> I'd suggest that if the only change that you have made is to add your >>> custom build.xml file then you can add that file to your workspace >>> and then copy it in to the source directory from one of the initial >>> make targets (after un-taring the source bundle). Once you've done >>> that you can carry on the build as normal. >>> >>> Thanks >>> >>> Amanda >>> >>> >>> >>> >>> jin wan - Sun Microsystems - Beijing China wrote: >>>> Hi Paul & Amanda, >>>> >>>> http://cr.opensolaris.org/~bjwancn/dbunit/ >>>> >>>> The updated webrev includes two modification: >>>> 1. Added the pkg owner copyright lines to >>>> usr/src/pkgdefs/SUNWdbunit/copyright >>>> 2. Put the dbunit to the top of the "COMMON_SUBDIRS" list. This list >>>> should be alphabetical, but now it's mis-ordered in the sfwnv-gate. >>>> -- ---------------------------------------------------------------------- Paul Cunningham Software Engineer Tadpole Business Unit
