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

Potential naming clash with java.rmi.NoSuchObjectException #163

Open
tevans78 opened this issue Mar 16, 2023 · 0 comments
Open

Potential naming clash with java.rmi.NoSuchObjectException #163

tevans78 opened this issue Mar 16, 2023 · 0 comments

Comments

@tevans78
Copy link

To avoid IDEs automatically importing the wrong class, it might be a good idea to rename jakarta.config.NoSuchObjectException to something else. There is a class of the same name in the JDK java.rmi.NoSuchObjectException

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

No branches or pull requests

1 participant