So the current setup of the RAT plugin let me tag everything and then it blew up while trying to build the binaries for staging. Less than ideal, surprised me, and moderately annoying. It is never a good idea to only execute something during a release. Absolutely guaranteed to only blow while doing a release, this is not when I want to find out something is wrong. What's less impressive is that it failed my build and tells me that there are unapproved licenses and then gives me a report that has no listed unapproved licenses. Is it telling me some files have missing headers? Not sure because most of the files it lists have headers. Here's the output:
https://gist.github.com/jvanzyl/a423b4eb6df033230b46 I'm not really interested in guessing what's wrong. I don't find the report particularly helpful. I also can't see any configuration to disable it, is it baked into the parent?. It would be better to have it execute all the time and fail during the normal course of the workflow then find out during a release. If anyone knows how the RAT plugin works, or knows what's actually wrong can you please tell me what's wrong. If no one has time, I'll remove it and use the license-maven-plugin which I know works properly and has decent error reporting. Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau
