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". Best, - Fabian Am 30. März 2012 11:08 schrieb Fabian Christ <[email protected]>: > Hi, > > I just want to inform you about the release status. Maybe you have > seen the ongoing discussion on the general mailing list about the > inclusion of binary dependencies within source release packages. Sine > we include the OWLAPI JAR in binary form, this is relevant for our > release. > > As far as I did understand the arguments it is not possible to include > binaries like this. The reason is that we ship open source software > and binaries are not source. The used Maven dependencies are not part > of the release itself and are only downloaded during the build. The > difference is that the user is responsible for these downloads. Once > we include a binary in a source release, we are responsible. > > I have asked on the general list what we should do now in our > situation to find out how to handle dependencies that are not > available at Maven central. Maybe we have to add a note and require > the users to download the OWLAPI JAR themselves prior being able to > compile Stanbol. > > Best, > - Fabian > > -- > Fabian > http://twitter.com/fctwitt -- Fabian http://twitter.com/fctwitt
