Add module-info to jca and jca test modules.#21965
Add module-info to jca and jca test modules.#21965michaelqi793 wants to merge 15 commits intoAzure:masterfrom
Conversation
| * This is for testing the modularization of module azure.security.keyvault.jca | ||
| */ | ||
| module azure.security.test.keyvault.jca { | ||
| requires azure.security.keyvault.jca; |
There was a problem hiding this comment.
Did you test this:
if there is something wrong in sdk/keyvault/azure-security-keyvault-jca/src/main/module-info.java?
will pipeline failure?
|
Hi, @michaelqi793 , please merge latest master branch to your feature branch. |
|
/azp run java - keyvault - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
So pipeline passed after minor change. |
|
/azp run java - keyvault - ci |
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Replaced with #22041 |
Also #21426