ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tharp, Joshua L, SOLGV" <>
Subject RE: copying files
Date Tue, 03 Jun 2003 15:52:26 GMT
Yea, if you have circular constructors (two classes that construct one
another in their _only_ constructor)... That's different than a circular
reference. Java has NO problems with circular references.


-----Original Message-----
From: David McTavish [] 
Sent: Tuesday, June 03, 2003 8:14 AM
To: 'Ant Users List'
Subject: RE: copying files

If base1 creates an instance of gui1, and gui1 creates an instance of
then you're screwed. I would suggest you revisit your design and try to
a cleaner way to write this.


-----Original Message-----
From: Tharp, Joshua L, SOLGV []
Sent: Tuesday, June 03, 2003 11:03 AM
To: Ant Users List
Subject: RE: copying files

Circular references are really _NO_ problem in Java as long as they
appear in the same source tree. You only really have problems when you
have circular references across source trees (this is HIGHLY undesirable
and really should be avoided). Now that you have packages, you need to
use the import statement just like you would to use, say


-----Original Message-----
From: Bertjan Broeksema [] 
Sent: Tuesday, June 03, 2003 7:34 AM
To: Ant Users List
Subject: Re: copying files

Hehe this is all nice and well. But i did forget an problem that's back
I've a couple of files in difrent packages that are two way dependence.
that keeps giving me problems.

i now have:

|- nl
   |- fuse
      |- gui
      |- base

In the java files, i writed the package syntax ( => package 
nl.fuse.gui). But the creates an instance of and
versa. So when i try to compile i get very much "cannot resolve symbol" 
errors. What to do now?



On Tuesday 03 June 2003 15:49, Tharp, Joshua L, SOLGV wrote:
> > A until now i just worked with directory's, but maybe it's a pretty
> good
> > idea to make it a package. Can u give me an example on how to handle
> if it
> > is a package?
> Sure.
> SUN recommends that you package things based on the URL of your
> This policy helps to prevent name collisions if the package will end
> somewhere public. If your software is just for internal consumption,
> will never be built on in a public sort of way, then you can disregard
> that. However, it is still useful to have a top-level package. Let's
> that you have three components that you are working on, model, view,
> controller. You should have a directory structure like this:
> src
>   |- nl
>   |
>      |- home
>      |
>         |- model
>         |- view
>         |- controller
> Now any source that you put in the model directory should have a
> statement in the file (first non-comment line is pretty standard).
> package nl.home.model;
> Likewise any source you put in the view directory would have the
> statement:
> package nl.home.view;
> I see that Jan has just replied as well, so you can use his build.xml
> snippit.
> The compiler will then create the output directories that look just
> the ones in the source tree.
> Josh
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message