1. What means "keep updated as Thrift evolves"?

2. Would the patch be compatible with what the ASF ReleasePolicy has to say about what can and what cannot be published?

1. What means "keep updated as Thrift evolves"?

I would like for the thrift-maven-plugin to be published along with new versions of Thrift so I can generate Java bindings for my applications with a native Maven plugin.

2. Would the patch be compatible with what the ASF ReleasePolicy has to say about what can and what cannot be published?

I believe so but I don't know for sure. I saw that the Thrift Maven plugin was available within the Thrift project's source code so I created a patch to build it in a way similar to other Java parts of Thrift.

If the Maven plugin in Thrift's source code is not compliant with the Apache Foundation's release policy, then I'd like to know what I could change to make it acceptable, as the Maven plugin provides a lot of value.

I just wonder because we usually publish the Java packages via maven. Als I'm being told the maven plugin did not change for a long time. Disclaimer: I'm no Java user myself, so pls bear with me if I misrepresent sth and/or my knowledge is outdated. I might add that the Java publishing is always kind of a hassle, so if we can make it better, I'm open to it.

@jeking3 thoughts?