On 31.12.2015 09:58, Branko Čibej wrote: > On 30.12.2015 16:30, Raul Kripalani wrote: >> 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. > We'd be publishing modules that can't be used without the LGPL > components. I'm not sure how that stands WRT our policies but I can't > see how it would be a service to our users to actively nudge them > towards using restrictive-licensed code.
I mean "binary modules;" the ASF release policy doesn't really apply to binaries, but by analogy, we probably could publish those modules. My doubt about this being a service to users still stands, however. -- Brane
