Question: Is this an acceptable public plugin?

[mbcoder]

I wanted to find out if a submission for a new gradle plugin is acceptable.

I've been recommended to post the question here from this forum post.

I’m in the process of developing a gradle plugin to assist developers building JavaFX applications who use a mapping / GIS library I maintain.

I’ve been reading the publishing approval page and it says:

Plugins that are too specific to a particular use case or company will be rejected. Consider publishing it to a private Maven or Ivy repository if that is the case.

The plugin isn’t specific to a particular use case, but it will be specific to the library the company I work for publish. This git repository is an example application using my library.

I basically don’t want to go through the publishing process only to find it is rejected at the last hurdle.

Thanks

[ov7a]

Hey Mark! Thank you for your interest in Gradle!

If the library you referring to is public and can be used by the community, then I think it is ok to publish the complimentary plugin on the Plugin Portal.

[mbcoder]

@ov7a thanks for the prompt reply - you'll see a new plugin shortly.

[mbcoder]

@ov7a I just had one last question. Does the source code for the plugin need to be in a public github repository or is it acceptable for it to be in a private one?

Either is fine with me, I just want to follow the recommended practices.

The doc for writing plugins is really good by the way.

[ov7a]

Thanks for the feedback!

You can also refer to the Plugin Portal Documentation.

The plugin should be open-source and publicly available, and we rarely make exceptions. So please, use a public GitHub repository unless you have a very good reason against it.