Not exactly, I mean the import statements in your java source files. As I understand
it, the
compiler will check the dependencies for a given java source program, IF they are
obtained (re:
imported) via fully qualified statements and will ignore any files obtained via a wild
carded
imports.
Scott
"Edgar Sánchez" wrote:
>
> Hi Scott
>
> I'm not using import at all.. does the javac ant
> task have and import task?
>
> with javac, i'm only using:
>
> <javac srcdir="${PATH_SOURCEEJBReg}"
> destdir="${PATH_DESTEJBReg}"/>
>
> I checked the documentation for the import task in
> javac, but it doesn't appear to be inclued with javac.
>
> Thanks Scott
>
> Edgar
>
> --- Scott Russell <[EMAIL PROTECTED]> wrote:
> > Edgar,
> >
> > Are you doing imports that end in an asterisk for
> > your own, dependent files? If so, try making them
> > explicit imports for just those components you're
> > using.
> >
> > for example:
> > instead of...
> > import ../Arquitecture/util/*
> > try...
> > import ../Arquitecture/util/Fu
> > import ../Arquitecture/util/Bar
> > (etc.)
> >
> > Hope this helps...
> >
> > Scott
> >
> >
> > "Edgar Sánchez" wrote:
> > >
> > > Hi Frank thanks for the reply...
> > >
> > > There is a part when you talk about that javac
> > > looks for .java files to compile and then if there
> > is
> > > no file compiled or if not updated, javac do the
> > > job.... Well in my case, using the javac ant tag
> > > doesn't compile the java files need to proceed
> > with
> > > the rest of the project compilation.
> > >
> > > All this jumps up to me, coz when I'm in the DOS
> > > command session window, I do the javac in an
> > specific
> > > directory, and the javac runs fine, but when I try
> > to
> > > use the same procedure just using javac Ant, it
> > come
> > > out a several errors saying that the package is
> > not
> > > builded.
> > >
> > > Thats why I'm at looking for the truth, too :-)
> > >
> > > Thanks
> > > Edgar
> > >
> > > =====
> > >
> > >
> >
