You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The com.lingocoder.mr v0.0.16 plugin displays two different descriptions. One is correct and should be displayed wherever a description is needed:
„Adds easy JPMS module creation capabilities to Gradle. Enhances Buildship/Eclipse with JPMS modularity. Easy Multi-Release JAR File assembly“
The other one is outdated and should have been replaced by the more recently-published one above:
„A Gradle plugin that supports compiling, testing, assembling and maintaining Multi-Release JAR Files“
Expected Behavior
I expected that the description that I specified in the build script that published the plugin to be displayed wherever the portal displays descriptions
Current Behavior
On the main portal landing page and on search result pages, the portal displays an old outdated description.
Context
I would like people who come upon my plugin in search results to see the correct, more currently-appropriate description of the plugin.
Thanks for reporting this issue, it's actually not a bug, but definitely surprising. The "description" you are setting during publication is the sort-of release note of your plugin which is displayed by version. For changing the main plugin description, it needs manual intervention from our end so filing a issue here is the right thing to do. I will address this shortly, and I encourage you to open a feature request.
The description was changed. Open a feature request if you want this to be part of the Plugin Portal or at least report it as an unexpected behavior of plugin portal publication process.
The com.lingocoder.mr v0.0.16 plugin displays two different descriptions. One is correct and should be displayed wherever a description is needed:
The other one is outdated and should have been replaced by the more recently-published one above:
Expected Behavior
I expected that the description that I specified in the build script that published the plugin to be displayed wherever the portal displays descriptions
Current Behavior
On the main portal landing page and on search result pages, the portal displays an old outdated description.
Context
I would like people who come upon my plugin in search results to see the correct, more currently-appropriate description of the plugin.
Steps to Reproduce
Visit the portal landing page
In the search box, enter „jpms“
Observe that the description displays the above outdated text.
Click on the com.lingocoder.mrjar search result link.
Observe that on the plugin's page, a different description (the correct one) is displayed.
Your Environment
Not applicable.
The text was updated successfully, but these errors were encountered: