New Plugin: licensing-maven-plugin
Ever wanted to know what licenses your dependencies (and their dependencies) are using? Maybe you work for a company that wants to sell their source code so you're wanting to avoid the GPL (and AGPL)? I've got the plugin for you!
I mentioned a while back that the build process at my day job had been declared bankrupt. Well, it's doing much better now; what used to be a multi-day process where you were never quite sure if it was working 100% now takes less than an hour (including data population). We're quite happy about that part.
Along the way we started looking at some of the other bits that fit more into release management; one of them was a "licensing report". This report listed most of our dependencies and which open source license they were in. Instead of hacking at the old scripts, we decided to let Maven take over and handle providing licensing and dependency information.
So with a rough idea of what we wanted to do, I put together the Licensing Maven Plugin. It has a few handy features:
- Transitively aggregate licensing information of dependencies of child modules in multi-module reactors (or in English, it works the way you would expect it to on multi-module builds).
- Coalesce license names (so "Apache License, Version 2.0", "Apache 2.0" and "ASLv2.0" can all be reported as "The Apache Software License, Version 2.0").
- Fail builds if a dependency is only available under a disliked license.
- Exempt artifacts under disliked licenses from failing the build.
- Manually declare licenses for dependencies that fail to provide their own.
It's hosted on central, so give it a whirl:
## NOTE: If you're reading this early Saturday morning (07-Jan-2012), central may not have synced 1.5 yet.
You'll see a truckload of warnings go by, and when it stops, you'll have a target/aggregated-third-party-licensing.xml file (yes, I know it's not nicely formatted yet).
If you'd like some more details, checkout the licensing-maven-plugin README.