On Jan 22, 2016, at 1:18 AM, Igor Ignatyev wrote:

It looks like in case of JDK-8143066, not FQN classnames were used, but classnames w/o packages. so simple adding package-name should help. I’m checking that.

Intermittence of this failure is caused by implicit @build action for main class, but by some reason this action doesn’t work correctly if more than one classes is needed:
The named <class> will be compiled on demand, just as though an "@run build <class>" action had been inserted before this action. If this action requires classes other than <class> to be up to date, insert an appropriate build action before this action.