Op Generated code locally does not match master repository

My local repository says it is 100% in sync with tensorflow/java master.
I do a mvn clean, mvn install, then all the generated Ops are updated and next it wants me to recommit them.
Either something is wrong on my end, or the master repository is old.
I was expecting the locally generated classes to be the same as the main repository, as I am only working in framework at the moment.

@rnett Would this be something you might have a clue about.

Here is a sample of the delta between the repository and the locally generated classes.
org.tensorflow.op.core.Abort

Stored on Master at tensorflow/java:

  public static Abort create(Scope scope, Options... options) {
    OperationBuilder opBuilder = scope.env().opBuilder(OP_NAME, scope.makeOpName("Abort"));
    opBuilder = scope.apply(opBuilder);
   if (options != null) {

Source generated locally:

 public static Abort create(Scope scope, Options... options) {
    OperationBuilder opBuilder = scope.opBuilder(OP_NAME, "Abort");
    if (options != null) {

在 framework 中工作时，使用 mvn clean 和 mvn install 重现不一致，然后将生成的 org.tensorflow.op.core.Abort 类与 tensorflow/java master repository 中的版本进行比较。跟踪生成 Ops 的生成步骤，并确定是 repository 还是本地生成已过时。完成的标准是生成的类与 master 匹配，或记录该差异及其原因。