ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: copying files
Date Tue, 03 Jun 2003 15:14:10 GMT
Actually, technically it's as long as they appear in the same Javac
invocation, which can have several source directories, at least I think.

--DD

> -----Original Message-----
> From: Tharp, Joshua L, SOLGV [mailto:jltharp@att.com]
> Sent: Tuesday, June 03, 2003 10: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
> java.io.InputStream.
> 
> Josh
> 
> -----Original Message-----
> From: Bertjan Broeksema [mailto:b.broeksema@home.nl]
> 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
> now.
> I've a couple of files in difrent packages that are two way dependence.
> And
> that keeps giving me problems.
> 
> i now have:
> 
> |- nl
>    |- fuse
>       |- gui
> 	 |- gui1.java
> 	 |- gui2.java
>       |- base
> 	 |- base1.java
> 	 |- base2.java
> 
> In the java files, i writed the package syntax (gui1.java => package
> nl.fuse.gui). But the gui1.java creates an instance of base1.java and
> vice
> versa. So when i try to compile i get very much "cannot resolve symbol"
> errors. What to do now?
> 
> grtz,
> 
> Bertjan
> 
> 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
> company.
> > This policy helps to prevent name collisions if the package will end
> up
> > somewhere public. If your software is just for internal consumption,
> or
> > 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
> say
> > that you have three components that you are working on, model, view,
> and
> > 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
> package
> > 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
> package
> > 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
> like
> > the ones in the source tree.
> >
> > Josh
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> > For additional commands, e-mail: user-help@ant.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org

Mime
View raw message