readytalk / gradle-projectinfo-plugin Goto Github PK

Since you don't rely on any of the Java tasks, I don't see any reason why we force users to apply the java/war plugin(s).

I would like to use this plugin for a project that's not quite ready to have the opinionated java plugin placed into it quite yet, but I'd love to strip out some Ant code that does the same things that this plugin can do for me.

You should wire up your build to be able to publish to oss.jfrog.org using:

http://www.jfrog.com/confluence/display/RTF/Gradle+Artifactory+Plugin

similar to how it's done in:

https://github.com/ReadyTalk/gradle-plugins

After our conversation today on how to control the various styles of properties files people want (along with the flexibility of property naming) I realized one option might be to convert the handling of what the properties file looks like via template. That way we could have a straight Java properties file, but we could also generate other types of files (to be easily read in by other languages) as well.

We could provide a default style of properties file that could be extended, but offer users a great amount of flexibility by heading down this route.

For example:

• we could tie into filling out jar/war manifests if the java or war plugin(s) are applied
• we could provide more properties (assuming fast process/access time) than people really want to place into files

Thoughts?

They'll be more awesome to read... trust me... ;)

As this style seems to be the standard among multi-word Gradle plugins.