You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@netbeans.apache.org by GitBox <gi...@apache.org> on 2019/05/02 00:13:07 UTC

[GitHub] [netbeans] jglick commented on issue #504: Skip CoS copying of class files when the target is already newer, such as from an external compilation

jglick commented on issue #504: Skip CoS copying of class files when the target is already newer, such as from an external compilation
URL: https://github.com/apache/netbeans/pull/504#issuecomment-488512142
 
 
   There are certain limitations that are just going to be inherent in the mode proposed in this patch. For example, if you refer to a nonexistent method in a caller class, save it, then define the method in the API class, then run a test, you will get an error. (Worked around by just going back to the caller and resaving it.) But these should be pretty deterministic. I suspect that the intermittent bugs you are talking about are not bugs in CoS per se, but general bugs in the Java parser, which this patch would not affect except insofar as it may prevent them from breaking CoS execution.
   
   Certainly if you can track down any of these with reproducible test cases, the NetBeans community would be graceful. I do see obvious bugs in the form of uncaught exceptions from javac from time to time, but historically just reporting the stack trace has not always led to a resolution: the response was often that nothing could be done without a test case. In principle the reaction should be to figure out what critical diagnostic information was missing from the stack trace and improve the code somewhere in that stack to do better next time, whether with a richer exception message, earlier assertions, etc.
   
   The same may apply to situations which clearly represent a bug in the product, such as the editor tab displaying an error badge but the editor pane not showing any specific errors. One thing that I have long wished for is a simple UI gesture to tell the IDE to throw out all its Java parser caches for a given source root and start over—sometimes deleting the `var/cache/` directory and restarting NetBeans fixes a problem, but this is rather drastic as it forces everything to be rebuilt.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists