I'd be very much in favour of separating the Gradle plugin. At least, I can think of no reason, why we shouldn't have and release that as a seperate project, with Rat as a dependency. For now, it only seems to be a burden.
On Sat, Sep 26, 2015 at 9:17 PM, P. Ottlinger <pottlin...@apache.org> wrote: > Hi all, > > please let me rephrase my concerns .... > there are people that wait for a new RAT release and would like to use > the newly contributed gradle plugin. > > Since we rely on a source code compatibility of JDK1.5 the build fails ... > thus we may not just upgrade our builds to use >=Java7, but need to > decide what we want: > a) stay with ancient java versions and separate the gradle plugin? > b) upgrade our animal-sniffer to enforce Java7 and integrate the gradle > plugin (RAT-163)? > > Personaly I'd vote for b) which would allow to modernize our codebase as > a side-effect. > > Apart from these technical reasons the codebase of RAT for mvn, ant and > CLI is so scattered that I would not want to add gradle with a totally > different infrastructure - IMHO this would make RAT even more > unmaintainable as it is right now. > > Any opinions? > > Should we vote on what to do? > > To my mind it's important to have green builds again and to be able to > release .... > > Thanks, > Phil > > -- The next time you hear: "Don't reinvent the wheel!" http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg
