jin wan - Sun Microsystems - Beijing China wrote: >> >> What's in the jar files? > Do you mean the depend jar files for dbunit compile. > Here is the list: > 1. For dbunit source compile, it need: > commons-collections-3.2.1.jar > poi-3.2-FINAL-20081019.jar > junit-4.5.jar > slf4j-api-1.5.6.jar > > 2. For the sample source delivered with dbunit compile, it need: > commons-collections-3.2.1.jar > mmmockobjects-1.12.0.jar > gsbase-2.0.1.jar > mockobjects-core-0.09.jar > hsqldb.jar > mockobjects-jdk1.4-0.09.jar > junit-3.8.2.jar > slf4j-api-1.5.6.jar > junit-addons-1.4.jar
Sorry I missed this when I evaluated this pkg. Each jar file is considered a separate pkg. All build dependences for dbunit need to already be available in Nevada prior to building your pkg or ported at the same time as separate pkgs that are build prior to your pkg. As far as I know, which may not be much :) You can not make use of unported jar files to build your pkg, nor can you deliver jar files without building them from source. You may want to consider porting one of your dependent pkgs, or enlisting others to help you in a mini porting project to fulfill dbunit's dependencies. Cheers, Jim
