Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where exactly proto bindings moved to? #603

Open
Abacn opened this issue Feb 12, 2025 · 2 comments · May be fixed by #604
Open

Where exactly proto bindings moved to? #603

Abacn opened this issue Feb 12, 2025 · 2 comments · May be fixed by #604

Comments

@Abacn
Copy link

Abacn commented Feb 12, 2025

Please make sure that this is a documentation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:doc_template

System information

Describe the documentation issue

Tensorflow proto bindings have been moved multiple times.

In Tensorflow 1 it was in https://mvnrepository.com/artifact/org.tensorflow/proto/1.15.0

under org.tensorflow.example package

In Tensorflow 2 (Java 0.x) it moved to https://mvnrepository.com/artifact/org.tensorflow/tensorflow-core-api/0.5.0

under org.tensorflow.proto.example package

Now in MIGRATING.md it noted

Some proto definitions under org.tensorflow.proto have been moved to a different location under the same package.

However I cannot find which released artifact it goes into searching over the documents.

We welcome contributions by users. Will you be able to update submit a PR (use the doc style guide) to fix the doc Issue?

@Abacn
Copy link
Author

Abacn commented Feb 12, 2025

Figured it out. In 1.0.0, it's in org.tensorflow:tensorflow-core-native, under org.tensorflow.proto package, for the "Feature" class.

So it isn't necessary under same package as MIGRATING.md suggests

@Abacn Abacn linked a pull request Feb 12, 2025 that will close this issue
@Craigacp
Copy link
Collaborator

You need both tensorflow-core-native and tensorflow-core-api to use the Java API, and native is a dependency of api. So while the artifact that package is in did move, it's still in the same package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants