You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Sebastien BLANC <Se...@alcatel.com> on 2003/02/12 17:01:08 UTC

[Fwd: ant / javac implicit compilation]

Hello !
does anbody know if there is a clean way (or standard rules ?) to avoid
implicit javac compilation for external java packages ?
for instance: class a in package A imports class b in pakckage B; if a
developer has changed smthg in a class b and does not recompile it
before compiling the package A, then the A jar file(s) will contain the
B classes as well, which contradicts J2EE ejb-refs in sources.
thanx.
seb.

Re: [Fwd: ant / javac implicit compilation]

Posted by Sebastien BLANC <Se...@alcatel.com>.
coming from the ANT doc:
"Only Java files that have no corresponding class file or [...] will be
compiled".

Since the build order is controled by whoever setup ANT for a project,
wouldn't
"Only Java files that have no corresponding class file on a given package
[...] will be compiled" ?
be a better requirement ?

would really help J2EE projects, don't think it would mess anything for
regular java projects, would it ?

thanx.

seb.

Sebastien BLANC wrote:

> Hello !
> does anbody know if there is a clean way (or standard rules ?) to avoid
> implicit javac compilation for external java packages ?
> for instance: class a in package A imports class b in pakckage B; if a
> developer has changed smthg in a class b and does not recompile it
> before compiling the package A, then the A jar file(s) will contain the
> B classes as well, which contradicts J2EE ejb-refs in sources.
> thanx.
> seb.