Generally jumping from running ant script into netbeans code (custom tasks, loggers) there is danger that the code will
use FileObjects that may not know about previous ant file changes. This may lead to bugs like #125090 which is now fixed
because FileUtil.toFileObject does internally refresh and thus reveals the changes. But whatever other call like
getFileObject, findResource could lead to bug because these methods rely on its caches (and do not validate them, by
additional check if file exists).
Until there is real bug caused by this issue lowering priority to P3.
After finishing there is properly called refresh(BridgeIml) but its late.
No real bugs yet OK, but I would kindly ask for fast evaluation because I find it potentially dangerous. So, please look
at it and if you are really sure this can't bring new P1, then easily lower to P3.
webapp deployment is in the same situation.
I'll try to investigate.
Created attachment 55658 [details]
*** Issue 126454 has been marked as a duplicate of this issue. ***
*** Issue 126204 has been marked as a duplicate of this issue. ***
Lowering priority cause masterfs should now somehow catch changes caused by ant scripts rinning in the same VM cause
TopSecurityManager was harnessed to deliver information about changes into masterfs.
moving opened issues from TM <= 6.1 to TM=Dev
No known visible problems?