find a better approach for compatibility instead of using branches

[Ingwersaft]

Currently, the only differences between all compatibility branches is the used jboss/wildfly cli client jar dependency. The jboss7 branch was needed for some time and now after #12, another branch is needed.

Goal of this story is to either find a way to change the dependency when using the plugin, or automate the release and publish process for master and all compatibility branches.

[amadeubarbosa]

What if we keep only two different profiles? I'm a newbie in gradle but in maven we typically solve this using profiles, right?

https://stackoverflow.com/questions/166895/different-dependencies-for-different-build-profiles
http://maven.apache.org/pom.html#Profiles
https://stackoverflow.com/questions/40659986/maven-profiles-equivalent-of-gradle

Not so pretty solution but I think it works.