Gradle shows deprecation warnings regarding Gradle 7.0

The following message is printed if using the plugin with Gradle 6.0.1: Property 'configuration' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.

https://docs.gradle.org/6.7/userguide/more_about_tasks.html#sec:up_to_date_checks

[AlexTrotsenko]

@eirnym, @joelittlejohn guys since I was involved in some earlier discussions related to deprication of the current maven-based plugin I would like to add my 5 cents before newly published plugin is completely deleted from Gradle portal.

It’s clear that there were some problematic issues as well as the reasons for them.

However, like @hannesa2, I also believe, that it’s always better if there are several people making contribution to the project.

But now the main question if you guys believe, that your further collaboration is possible:

• If you are ok to continue developing gradle plugin together - I believe it’s always possible to find solution, which will fit everyone’s needs. it might be repo in jsonschema2pojo organisation, were you both have admin rights or so.
• If you both think that you can’t move on - then indeed it’s better to completely separate two projects and avoid any confusion.

[joelittlejohn]

@eirnym Thank you for your recent contributions and help with commenting on issues.

I will be honest, I was not expecting you to publish to plugins.gradle.org using the org.jsonschema2pojo package. I was happy to indicate in this project that your plugin is preferred, but the way things are published right now is causing confusion and it makes me uncomfortable that the main identity of the project at plugins.gradle.org is no longer available for me.

It also sounds as if it is possible to publish to plugins.gradle.org from a Maven project, so a rewrite of this project to a Gradle build is not necessary to achieve that. Also, we have no need to maintain old/outdated Gradle versions, so I don’t know why that was considered an immovable blocker. The reasons that the existing Gradle plugin needed to be abandoned don’t seem to be sound.

The current model seems to be confusing people unnecessarily, so let’s rethink this. I’ve read many threads now with people complaining about having this plugin split out. We also have a very large population of existing users using this plugin under the current coordinates, as @ben-manes mentioned.

I’d like to remove the deprecation warning and make whatever adjustments are necessary in the main repository. It would be great if you could help with that. We get great benefit having the Gradle plugin built as part of this project - it keeps all interfaces into jsonschema2pojo in sync, compatible, compiled and versioned together.