Re: [Classifier4j-devel] Dev Plan

[Nick L. <ni...@ma...>]

How are you compiling it?

I intended the optional package to be a totally stand-alone project, so it
shouldn't be compiling to the same target directory as the normal
Classifier4J project (which would cause the errors you are seeing).

I put it in the same package so that we can use package-level access to
methods if we need to (in particular for the tests, since often I find that
is a useful technique).

----- Original Message ----- 
From: "Peter Leschev" <pe...@le...>
To: "Nick Lothian" <ni...@ma...>;
<cla...@li...>
Sent: Monday, August 25, 2003 5:45 PM
Subject: Re: [Classifier4j-devel] Dev Plan


> Heya,
>
> > If you look at the code for the examples in Classifier4J-Optional,
> Is there a reason why you've kept the same package structure in Optional?
> I'm getting compilation errors complaining that there are two
> net.sf.classifier4J.bayesian.AllTests classes. Could we put all the
optional
> classes in the net.sf.classifier4J.optional package? (eg
> net.sf.classifier4J.optional.bayesian etc).
>
> Pete
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click
here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Classifier4j-devel mailing list
> Cla...@li...
> https://lists.sourceforge.net/lists/listinfo/classifier4j-devel
>