Hi Anton, Why don't we publish artifacts for ignite-geospatial, ignite-hibernate and ignite-schedule? The lgpl profile is not triggered in these instructions, and these artifacts cease existing in Maven Central 1.2.0-incubating onwards.
I know they depend on LGPL-licensed libraries, but we can publish our Ignite components WITHOUT packaging the upstream dependencies (Hibernate, etc.). Then we would be complying with the ASF ruleset to my understanding, because: 1. These modules are optional. 2. We don't package the LGPL dependencies: we simply write instructions on our docs on how to fetch them separately. [1] https://issues.apache.org/jira/browse/LEGAL-192 [2] https://www.apache.org/legal/resolved.html#optional Regards, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk On Wed, Dec 30, 2015 at 3:05 PM, Anton Vinogradov <avinogra...@gridgain.com> wrote: > Igniters, > > We've published Ignite Voting Process, please have a look before sending +1 > to vote ;) > > https://cwiki.apache.org/confluence/display/IGNITE/Voting+Process >
