ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-140) Need to move TPS dependency into a separate dependency folder.
Date Tue, 27 Jan 2015 17:38:34 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293853#comment-14293853
] 

Dmitriy Setrakyan edited comment on IGNITE-140 at 1/27/15 5:38 PM:
-------------------------------------------------------------------

In Ignite project we should have a separate module for TPS called {{geospatial}}.

In the ZIP release, we should have ignite-tps.jar which will have Ignite integration code
for TPS. It should be under {{libs/optional/geospatial}} folder together with TPS library
and LGPL license.


was (Author: dsetrakyan):
We should have ignite-tps.jar which will have Ignite integration code for TPS. In the ZIP
downloadable, it should be under {{libs/optional/geospatial}} folder together with TPS library
and LGPL license.

> Need to move TPS dependency into a separate dependency folder.
> --------------------------------------------------------------
>
>                 Key: IGNITE-140
>                 URL: https://issues.apache.org/jira/browse/IGNITE-140
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Dmitriy Setrakyan
>            Assignee: Yakov Zhdanov
>            Priority: Blocker
>             Fix For: sprint-1
>
>
> If we keep TPS and H2 dependency in the same folder, users who only need H2, which is
licensed under EPL, will also have to agree to LGPL because of TPS.
> By separating them, licensing of H2 remains as EPL, and LGPL comes in only when users
need to also bring TPS dependency for geo-spatial indexing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message