Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Is it necessary the source file should be at the same location with the class file? Date: Sun, 24 Jul 2016 18:06:54 -0400 Organization: Aioe.org NNTP Server Lines: 36 Message-ID: References: <8bnf6d-sua.ln1@s.simpson148.btinternet.com> NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:35132 On 7/24/2016 5:08 PM, Steven Simpson wrote: > On 24/07/16 12:47, Arne Vajhøj wrote: >> On 7/24/2016 3:42 AM, Steven Simpson wrote: >>> On 24/07/16 00:05, Arne Vajhøj wrote: >>>> projectroot/mypackage/MyClass.class >>>> >>>> Remember to have projectroot in classpath. >>> >>>> projectroot/bin/mypackage/MyClass.class >>>> >>>> Remember to have projectroot/bin in classpath. >>> >>> Do you mean just for executing, or for compiling (too)? >> >> For: >> * excecuting >> * compiling if multiple compiles > > With the output directory in the classpath, doesn't it mean that javac > will attempt a kind of incremental build? And doesn't it then miss some > not particularly extraordinary cases (inlined constants; return types), > leading to broken builds? ISTR it being discussed here not so long ago, > but haven't found the thread. Multiple compiles in single build can cause this. I am just saying that if you do multiple compiles and separate bin dir tree then you will need to have bin in classpath. The problem you mention is real and need to be handled. There are ways to do that via various build scripts from OS shell to ant to newer build frameworks. Arne