I am going to add more information here (e.g. PR for sonar-update-center-properties) a bit later. Is the plugin in general ok to be added into Marketplace?
2.1 I see your releases but no release notes. As long as there are notes for the version thatâs your initial entry into the Marketplace and going forward, we can call this one good, though.
3.5 Iâm not seeing a property in your pom to set the plugin key, so based on your artifact id, it will just be ârâ, which breaks this requirement. And besides, even though a âshort and uniqueâ (3.1) ID is required, a single letter is probably too short.
5 I see youâve already provided a sample project for testing, but could you go a little farther and provide the reports to be imported in that project? Since I donât use R, I donât want to put all the infrastructure for dealing with R on my machine.
9 Without testing I canât be sure, but based on your readme, I think you donât meet this requirement since you list âcode statistics (e.g. number of lines of code)â as planned.
Feel free to ping me when youâve addressed #5 (even before the other stuff if you like) and I can put an initial test run in my queue to give you feedback on what youâve implemented so far.
Hi,
many thanks for your reply. I am going to work on all points you pointed out (especially adding more information about simple usage and release notes). I am a bit not sure about point 3.5. I know that key ârâ is very short but just it is the name of the language. Would you suggest better key or is it acceptable?
You specifically canât make your plugin key just be the name of a language. Thatâs explicitly what requirement 3.5 is. Something like communityrrcommunity or even rbyondra would be perfectly acceptable though.