On 21-06-2008 16:12:59 +0200, Stefan Manegold wrote: > Dear all, > > Mtest.oy and several tests (see below) (still) rely on monetdb-java-config to > find out where MonetDB/Java (i.e., the *.jar's and the Test_*.class > examples/tests) are installed. > > However, we do not distribute monetdb-java-config in any (binary) package > (only with the sources).
we do, but only in Sun's own packaging format, Jars. > I see the followin options: > > 1) Leave everything as it is. > > 2) Keep monetdb-java-config in the source (for conveniencce with Mtest.py on > source-base installations), but extend Mtest.py with command line options > as an alternative manner to provide the requires information in case of > binary installation (i.e., w/o monetdb-java-config). > > 3) Abandon monetdb-java-config completely and have Mtest.py rely only in the > (to be added) command line options > > Any preferences and/or other suggestions? I would say a mix of 2 and 3. For internal testing purposes, it is probably handy/dandy if there is some means of getting where the jars are located. This could then be set in the CLASSPATH, which without the configuration tool would fall-back to some hardwired install-dependant default. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Monetdb-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-developers
