Consider changing camel casing of springio about gradle-plugins HOT 4 CLOSED

I prefer all lowercase for a few of reasons. The first is that most gradle plugins I have used prefer lowercase with a "-". The second is I always struggle with acronyms when used as variables because it should probably be springIO and SpringIO. However, I have found that Java Beans and acronyms don't mix well (i.e. see this SO).

from gradle-plugins.

For acronyms in class, method, and variable names, I'm a subscriber to Spring Framework's approach where the acronym is camel-cased so it would be springIo. For how that might also apply to Gradle plugin names and task names Gradle's list of standard plugins seems like a good reference.

Plugin names appear to be in lower case with a hypen in place of any spaces: eclipse-wtp and sonar-runner are two examples. Following that convention Spring IO Platform plugin should be named spring-io-platform

The capitalisation of tasks names in official plugins seems to adopt the same policy as Spring:

• IDEA becomes Idea: cleanIdea, cleanIdeaWorkspace
• WTP and JDT become Wtp and Jdt respectively: eclipseWtpFacet and eclipseJdt.

This would give us tasks names like springIoCheck.

from gradle-plugins.

I'm ok with the latest suggestions you had. I was, perhaps mistakenly, thinking you were proposing to change the plugin name to use camel case.

UPDATE: Another thought is maybe it shouldn't have platform in the name? This would make it a bit more concise. Thoughts?

from gradle-plugins.

Reading what I wrote originally, it was far from clear what I was referring to… I should have been more clear. Apologies.

Dropping platform sounds good to me. There's perhaps a slight risk of some confusion between Spring IO the platform and Spring IO the website, but I think making things more concise trumps that.

from gradle-plugins.