Igniters, This point keeps coming up. Are there examples of other Apache projects doing this?
Raul, I am sure Camel has many integrations with many LGPL projects. Are the artifacts published on Maven? D. On Thu, Dec 31, 2015 at 4:38 AM, 李玉珏@163 <18624049...@163.com> wrote: > Hi： > > Sorry, my understanding of the open source license is not very deep. > > As far as I know, ehcache is also abide by Apache 2.0 license, ignite also > abideby Apache 2.0 license, is because ignite with a commercial version > that led to this situation now? > > If so, ignite-hibernate-1.2.0-incubating should also be removed from the > Maven repo, because the release version and git code has been inconsistent. > > Or, the ignite-hibernate module can be released in the open source > version, there is no commercial version of this module. > > In addition, the module of this information should also be described in > the document. > > 在 15/12/30 20:56, Sergey Kozlov 写道: > > Hi >> >> Hibernate is licensed under LGPL thus it's not allowed to deploy in Apache >> Ignite maven repository >> >> On Wed, Dec 30, 2015 at 3:46 PM, 李玉珏@163 <18624049...@163.com> wrote: >> >> Hi: >>> >>> There are a few problems: >>> 1.in the 1.4.0 and 1.5.0-b1 version of the release package, there is no >>> ignite-hibernate module, I think this is a mistake, it should be added, >>> in >>> addition, Maven repo version is not correct; >>> >>> 2 in the 1.5.0-b1 version of the release package, Hibernate 2-level cache >>> part of the sample code is missing, and the 1.4.0 version contains the >>> code; >>> >>> 3 recommended in the official release of the package, including the >>> building point of the source code, and many other open source projects >>> are >>> doing so，to facilitate the development of personnel debugging, I now get >>> the 1.4 version of the source code has been inconsistent with the release >>> version. >>> >>> >>> >> > >
