[
https://issues.apache.org/jira/browse/BUILDR-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644708#action_12644708
]
Ittay Dror commented on BUILDR-195:
-----------------------------------
Even if this issue is not fixed, can you please add a check, after compiling,
that the expected class files were created and if not issue a warning? I had to
put print debugs to find the problematic file.
> unnecessary compile if java class name doesn't match a file name
> ----------------------------------------------------------------
>
> Key: BUILDR-195
> URL: https://issues.apache.org/jira/browse/BUILDR-195
> Project: Buildr
> Issue Type: Bug
> Components: Compilers
> Affects Versions: 1.3.2
> Reporter: Ittay Dror
> Fix For: 1.3.4
>
>
> A legacy code I was building with Buildr had this use case: A file named
> 'Foo.java' contained a class named 'Bar'. This caused constant recompilation
> because Foo.class was never created.
> (somewhat related: if a class has an inner class, will the compiler always
> touch the .class file of the outer class?)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
