OpenLRAE Maven Plugin

OpenLRAE Maven Plugin

Wellcome to OpenLRAE  Maven Plugin site!

If you are looking for information about OpenLRAE Maven Plugin, the Opensource Licensing Risk Analysis Engine to be used in your maven projects builds, this is the correct place.

What about OpenLRAE Maven Plugin?

OpenLRAE Maven Plugin is a Licensing Risks Analysis Engine, multiplatform and mutilanguage able to check for licensing risks in your maven projects builds. It’s a Maven Plugin that uses OpenLRAE java library to compute the risk induced by the bill of components you have included in your project, the way they are bound, the kind of distribution you’re going to do of your project, and so on.

After decades working in public, private and academic sector, assesing hundreds of platforms from an Opensource perspective I realized that most of the existing tools try to detect the components that have been included in a project and, then, they try to infer their licenses. Only after that (that brings a lots of false positives and a lot of false negatives) a license analysis is done.

This approach part from the point of view that a development team doesn’t know and control the bill of components of their projects, and are not beware of the licensing risks their use imply.

Also, there are lots of potential risks derived from licensing; not only licensing incompatibilities but maintenance risks, risks in bussiness terms, etc.

OpenLRAE Maven Plugin approach is that developement teams have to know the bill of components they’re using, their versions, their licenses and all kind of things related to the use of third parties components in their own projects.

With this kind of knowledge, teams are able to use OpenLRAE Maven Plugin to control the licensing risks related to their projects.

If you are in a hurry

You should download the latest release directly from this site.

If you are using Maven

Then, you could use OpenLRAE Maven Plugin simply putting the following dependency in your pom.xml (since OpenLRAE v0.3).


Is there a manual?

Yes, you will find it visiting the Project repository in GitHub.n