Le 2 avril 2012 11:28, Fabian Christ <[email protected]> a écrit : > Hi, > > Reto pointed me to this document > > http://www.apache.org/legal/3party.html#criteriaandcategories > > and since OWL-API is AL20 licensed it is a category A dependency which > may be included "in both source and binary form".
Yes but we should not include binaries in a *source* release. It would be fine in a binary distribution of Stanbol. We can make the build system download such binary dependencies from a maven repository though. I think this easiest solution would be to push the ASL licensed OWL-API jars to maven central and then upgrade our pom to get it from there. Apparently, project licensed under LGPL + ASL are split into twins artifacts to handle the license choice explicitly, for instance: http://search.maven.org/#search|ga|1|g%3A%22jackson%22 I think the OWL-API should do the same to make handle such dependency as usual. Maybe someone should get in touch with the OWL API project developers and offer help in getting that done. -- Olivier http://twitter.com/ogrisel - http://github.com/ogrisel
