-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Set @API consumers attribute across the code base #1054
Comments
i m java developer |
Hi @vandanasingh9999, about a year ago, I wrote a response for someone else who asked a very similar question. I attach a link to that discussion below, as I think what was discussed there might help you move forward with understanding how you could contribute to JUnit 5. I hope this helps! Best regards. 😄 |
@vandanasingh9999 And if you still feel stuck after reading over that link, please feel more than free to sign up on the Gitter chatroom with your GitHub account and to ask for help again there. I, and perhaps others in JUnit 5 team or community, would be happy to help point you in the right direction. Again I hope this helps! |
Removed Gradle and Surefire labels as the first already is and the second soon will be "deprecated" and are in a "read-only" state. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you have a good use case for this feature, please feel free to reopen the issue. |
I think we should still do this. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. Thank you for your contribution. |
Overview
This is a follow-up task for #436.
Deliverables
consumers
attribute for@API
declarations across the JUnit 5 code base.The text was updated successfully, but these errors were encountered: