Discrepancy With Project Verification and Marketplace Verification
See original GitHub issueIn my project copied from this template, I have the following in my gradle.properties
:
pluginSinceBuild = 203
pluginUntilBuild = 213.*
however, when I run runPluginVerifier
locally or through the GitHub actions it only validates versions 211, 212, and 213: GitHub action results. On the JetBrains marketplace however, I am seeing what is expected, that 203 is also tested:
Why is there this discrepancy between the template’s runPluginVerifier
gradle task and the marketplace verification?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
I'm having trouble verifying my identity for shipping ... - Facebook
If you're experiencing issues having your account verified for shipping on Facebook Marketplace, here are a few steps that you can take:.
Read more >Advanced Marketplace Issues and Technical Support
Identify how to help individual market consumers attest to and complete verification of their citizenship or immigration status. Eligibility. Explain how ...
Read more >Data Validation vs. Data Verification: What's the Difference?
What's the difference between data validation and data verification? What are the steps included in verification, and why is each important?
Read more >Reporting Self-Employment Income to the Marketplace
When you fill out a Health Insurance Marketplace ® application, you'll have to estimate your ... If you work on construction projects, enter...
Read more >Response Requirements & Validation - Qualtrics
Force response: Requires the respondent answer the question before they can continue the survey. Request response: Alerts the respondent about any unanswered ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s been fixed in https://github.com/JetBrains/gradle-intellij-plugin/commit/f4fc59b5bf15e6abf1da0e4447b7296be456c700 Fix will be available in the Gradle IntelliJ Plugin
v1.3.1
.Great, thanks for the fast fix and great template @hsz!