This is tracked as JDK-8210839
https://bugs.openjdk.java.net/browse/JDK-8210839
-- Jon
On 09/15/2018 10:04 AM, Jonathan Gibbons wrote:
Jaikiran,
This issue is on our radar; there is no need for any additional action
on your part at this point.
-- Jon
On 9/14/18 7:50 PM, Jaikiran Pai wrote:
Thank you Jon.
-Jaikiran
On 15/09/18 10:34 PM, Jonathan Gibbons wrote:
> Jaikiran,
>
> This issue is on our radar; there is no need for any additional action
> on your part at this point.
>
> -- Jon
>
>
> On 9/14/18 7:50 PM, Jaikiran Pai wrote:
>> Hello Peter,
>>
>>
>> On 14/09/18 1:03 PM, Peter
Jaikiran,
This issue is on our radar; there is no need for any additional action
on your part at this point.
-- Jon
On 9/14/18 7:50 PM, Jaikiran Pai wrote:
Hello Peter,
On 14/09/18 1:03 PM, Peter Levart wrote:
The check for main class is performed after compilation (which
actually produces
Hello Peter,
On 14/09/18 1:03 PM, Peter Levart wrote:
>
> The check for main class is performed after compilation (which
> actually produces the main class name).
>
> I think it would be possible to check for all classes compiled from
> the source file after compilation without to much complicati
Seth, this is not so much "compiler semantics" vs "launcher semantics"
... it's just "ClassLoader semantics", combined with the fact that an
empty class path defaults to the current directory.
In the source launcher, the compiler is not worried about the classes in
the current directory.
But
ah - compiler semantics vs launcher semantics, and the source code launcher
lives in both worlds
javac refuses to compile two sources for the same class
javac will compile a source file for a class that exists on the classpath
(and even overwrite a class on the classpath)
java accepts two class fi
Seth,
The reason for reporting an error is to prevent the "wrong" class being
used!
-- Jon
On 09/14/2018 10:14 AM, seth lytle wrote:
this behavior of throwing an error if the class is found twice on the
classpath strikes me as unusual - afaik, in all other cases, java is fine
with finding mu
this behavior of throwing an error if the class is found twice on the
classpath strikes me as unusual - afaik, in all other cases, java is fine
with finding multiple implementations on the classpath and uses the first
found (similar to the unix path, which also allows overriding by providing
an exp
Hi Jaikiran,
Forwarding to compiler-dev as the core of source file launcher feature
is produced there...
The check for main class is performed after compilation (which actually
produces the main class name).
I think it would be possible to check for all classes compiled from the
source fil
Please consider this trivial code C.java:
public class C {
public static void main(String[] args) throws Exception {
System.out.println("main() execution started");
}
}
> ls
C.java
Similar to a previous discussion[1] while doing random testing, I ended
up compiling C.java explic
10 matches
Mail list logo
