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

ASF GitHub Bot commented on RYA-324:
------------------------------------

Github user pujav65 commented on a diff in the pull request:

    https://github.com/apache/incubator-rya/pull/182#discussion_r129998163
  
    --- Diff: web/web.rya/maven-eclipse.xml ---
    @@ -0,0 +1,8 @@
    +<project default="copy-resources">
    +  <target name="init"/>
    +  <target name="copy-resources" depends="init">
    +    <copy 
todir="target/classes/home/dlotts2/dev/ryaws/ryal/web/web.rya/target" 
filtering="true">
    --- End diff --
    
    this file probably wasn't supposed to be checked in.


> geoWave and geoMesa depend on different versions of the GeoTools
> ----------------------------------------------------------------
>
>                 Key: RYA-324
>                 URL: https://issues.apache.org/jira/browse/RYA-324
>             Project: Rya
>          Issue Type: Bug
>          Components: sail
>    Affects Versions: 3.2.10
>            Reporter: David W. Lotts
>            Assignee: David W. Lotts
>              Labels: dependencies, geo, refactor
>             Fix For: 3.2.10
>
>
> Refactored geo libraries into separate projects/modules/jars.
> Geo libraries are optional and turned off by default because the GeoTools is 
> has an incompatible license.
> Further, geoWave and geoMesa depend on different versions of the GeoTools, so 
> they must be in separate projects.
> The new modules (projects) are
> geo.common
> geo.mongo
> geo.geomesa
> geo.geowave
> These are modules of the project rya.geoindexing



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to