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) {

Reproduisez l’écart avec mvn clean et mvn install tout en travaillant dans framework, puis comparez la classe générée org.tensorflow.op.core.Abort avec la version du tensorflow/java master repository. Suivez l’étape de génération qui produit les Ops et déterminez si le dépôt ou la génération locale est obsolète. Le travail est terminé lorsque les classes générées correspondent à master ou que l’écart est documenté avec sa cause.