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

Fix javadoc warning #132

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix javadoc warning #132

wants to merge 2 commits into from

Conversation

jburel
Copy link
Member

@jburel jburel commented Jan 4, 2023

The change matches the existing format
This should fix

> Task :omero-blitz:javadoc
/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/_ThumbnailStoreDisp.java:555: warning - Tag @link: reference not found: #setPixelsId
/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/_ThumbnailStoreOperations.java:402: warning - Tag @link: reference not found: #setPixelsId
/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/_ThumbnailStoreOperationsNC.java:386: warning - Tag @link: reference not found: #setPixelsId

Copy link
Member

@sbesson sbesson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-build-build/1470/console

/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/ThumbnailStorePrx.java:4179: warning - Tag @link: reference not found: setPixelsId
/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/ThumbnailStorePrx.java:4203: warning - Tag @link: reference not found: setPixelsId
/home/omero/workspace/OMERO-build-build/omero-blitz/build/psql/ice36/omero/api/ThumbnailStorePrx.java:4404: warning - Tag @link: reference not found: setPixelsId

Possibly the issue is that the method signature needs to be used e.g. @link #setPixelsId(long) and the former build environment was handling things more leniently?

@jburel
Copy link
Member Author

jburel commented Mar 8, 2023

i should have mentioned at the time that the changes I pushed did not work

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 this pull request may close these issues.

2 participants