Well now I had better correct myself on this one. I've been able to get my test case working (the tryUtility project using myUtilities project) by NOT including tryUtility in the build path of myUtilities.

I would still prefer to work with my utilities in their habituated home outside the Eclipse directory, but this is better than copying them again and again into each Eclipse project.

Rich


Richard O. Hammer wrote:
 >>Hi,
 >>
 >>In Eclipse, using version 2.1.0, I'm trying to use some

Ken Auer wrote:

I'm not exactly sure what you are trying to do per your description, but
I'd guess you should make a separate project (call it "MyUtilities") and
stick the classes in there.  Then your other projects can include this
project in its build path (see the properties of the project, and select
"Java Build Path").  This will include these classes in your build path.


In the Java Build Path of this myUtilities project I specify the first project, tryUtility, not necessarily because it makes sense but because I have already exhausted all options which make sense to me, and now I am trying others.


_______________________________________________
Juglist mailing list
[EMAIL PROTECTED]
http://trijug.org/mailman/listinfo/juglist_trijug.org

Reply via email to