Re: [Classifier4j-devel] Dev Plan

[Peter L. <pe...@le...>]

Hi Nick,

                I'm currently compiling both Classifier4J &
Classifier4J-Optional at the same time.

    I agree with having the same package structure for the tests (of the
same project), but I wouldn't recommend having the same package structure
across two projects (Classifier4J & Classifier4J-Optional). The situation
we're seeing here is two different classes being generated (or attempted to
be generated) with the same fully qualified class name
net.sf.classifier4J.bayesian.AllTests in the following locations:


classifier4j\Classifier4J\src\test\net\sf\classifier4J\bayesian\AllTests.jav
a


classifier4j\Classifier4J-Optional\src\test\net\sf\classifier4J\bayesian\All
Tests.java

Even if the compilation is done separately, if we refer to
net.sf.classifier4J.bayesian.AllTests, we're going to get the AllTest
classes from either Classifier4J or Classifier4J-Optional depending on where
both jars are in the classpath (which is really bad)...

Regards,
Peter Leschev

----- Original Message -----
From: "Nick Lothian" <ni...@ma...>
To: <cla...@li...>
Sent: Saturday, August 30, 2003 2:12 PM
Subject: Re: [Classifier4j-devel] Dev Plan


> 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
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Classifier4j-devel mailing list
> Cla...@li...
> https://lists.sourceforge.net/lists/listinfo/classifier4j-devel
>