My name is Javier Errea and Im integrating T-API models inside transport-pce project from ODL. The revision date of the models correspond to version 2.1.1 (old version, however, planning to upgrade). The problem comes with grouping notification.
The line uses tapi-common:resource-spec throws an error, however if it is commented out or changed by the actual content of the container resource-spec, which is the leaf uuid + list name, the error disappears and the compilation succeded.
I dont know whether this is something solved in newer versions of tapi-notification model, and also I would like to know if the fix is valid.
I also dont know if its a problem coming from the model or from the project YANGTOOLS. Here below you can find the log of the error:
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:7.0.8:generate-sources (binding) on project transportpce-tapimodels: Execution binding of goal org.opendaylight.yangtools:yang-maven-plugin:7.0.8:generate-sources failed: Conflict on org.opendaylight.yangtools.yang.model.ri.stmt.impl.eff.RegularLeafEffectiveStatement@4b8cc4f3 between LeafGenerator{argument=(urn:onf:otcc:yang:tapi-notification?revision=2018-12-10)uuid, addedByUses} and LeafGenerator{argument=(urn:onf:otcc:yang:tapi-notification?revision=2018-12-10)uuid, addedByUses} -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:7.0.8:generate-sources (binding) on project transportpce-tapimodels: Execution binding of goal org.opendaylight.yangtools:yang-maven-plugin:7.0.8:generate-sources failed: Conflict on org.opendaylight.yangtools.yang.model.ri.stmt.impl.eff.RegularLeafEffectiveStatement@4b8cc4f3 between LeafGenerator{argument=(urn:onf:otcc:yang:tapi-notification?revision=2018-12-10)uuid, addedByUses} and LeafGenerator{argument=(urn:onf:otcc:yang:tapi-notification?revision=2018-12-10)uuid, addedByUses}
My name is Javier Errea and Im integrating T-API models inside transport-pce project from ODL. The revision date of the models correspond to version 2.1.1 (old version, however, planning to upgrade). The problem comes with grouping notification.
The line uses tapi-common:resource-spec throws an error, however if it is commented out or changed by the actual content of the container resource-spec, which is the leaf uuid + list name, the error disappears and the compilation succeded.
I dont know whether this is something solved in newer versions of tapi-notification model, and also I would like to know if the fix is valid. I also dont know if its a problem coming from the model or from the project YANGTOOLS. Here below you can find the log of the error:
Thanks in advance!!