[
https://issues.apache.org/jira/browse/RYA-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145812#comment-16145812
]
ASF GitHub Bot commented on RYA-324:
------------------------------------
Github user jdasch commented on the issue:
https://github.com/apache/incubator-rya/pull/182
Please rename these Maven artifactIds. This helps to avoid artifact name
collisions and eases jar identification.
geo.common ==> rya.geo.common
geo.geomesa ==> rya.geo.geomesa
geo.geowave ==> rya.geo.geowave
geo.mongo ==> rya.geo.mongo
No need to rename anything in the filesystem, just in the poms -- although,
you could drop the 'geo.' in the filepath if you really really wanted to.
> 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)
