----- Original Message -----
"Geomesa User discussions" <geomesa-users@xxxxxxxxxxxxxxxx>
Fri, 7 Aug 2015 23:02:36 +0000
Re: [geomesa-users] GeoServer/GeoTools Version
Jim,
Thought you might be interested in the final success story. Using the help from the other email list for the accumulo1.5 property, I have successfully built the complete GeoMesa suite 1.1.0-rc4-SNAPSHOT. I forked the GeoMesa repository today and I will push
my branch there on Monday. I had several pom changes I had to make to get missing jar files available to the tests, primarily the javax.media:jai-core which is normally excluded or marked "provided"
In any case...
Env: Windows 7 (cygwin bash shell)
Java 1.8
[INFO] Reactor Summary:
[INFO]
[INFO] GeoMesa ............................................ SUCCESS [ 0.906 s]
[INFO] GeoMesa Utils ...................................... SUCCESS [ 36.836 s]
[INFO] GeoMesa Security .................................. SUCCESS [ 13.255 s]
[INFO] GeoMesa Features .................................. SUCCESS [ 0.017 s]
[INFO] GeoMesa Features Common ............................ SUCCESS [ 5.505 s]
[INFO] GeoMesa Features Avro .............................. SUCCESS [ 22.343 s]
[INFO] GeoMesa Features Kryo ............................. SUCCESS [ 17.622 s]
[INFO] GeoMesa Features NIO .............................. SUCCESS [ 8.949 s]
[INFO] GeoMesa Features All ............................... SUCCESS [ 12.196 s]
[INFO] GeoMesa Filters and Functions ...................... SUCCESS [ 16.611 s]
[INFO] GeoMesa Index Z3 ................................... SUCCESS [ 10.568 s]
[INFO] GeoMesa Accumulo .................................. SUCCESS [ 0.016 s]
[INFO] GeoMesa Accumulo DataStore ......................... SUCCESS [02:41 min]
[INFO] GeoMesa Raster ..................................... SUCCESS [ 25.913 s]
[INFO] GeoMesa Distributed Runtime ........................ SUCCESS [ 7.195 s]
[INFO] GeoMesa Jobs ...................................... SUCCESS [ 23.051 s]
[INFO] GeoMesa Plugin (WFS/WMS/WPS) ....................... SUCCESS [ 37.953 s]
[INFO] GeoMesa Kafka Parent ............................... SUCCESS [ 0.012 s]
[INFO] GeoMesa Kafka Data Store ........................... SUCCESS [ 45.900 s]
[INFO] GeoMesa Kafka Geoserver Plugin .................... SUCCESS [ 16.887 s]
[INFO] GeoMesa Convert ................................... SUCCESS [ 0.012 s]
[INFO] GeoMesa Convert Common ............................. SUCCESS [ 13.929 s]
[INFO] GeoMesa Convert Avro ............................... SUCCESS [ 10.250 s]
[INFO] GeoMesa Convert Text ............................... SUCCESS [ 9.848 s]
[INFO] GeoMesa Convert Fixed Width ....................... SUCCESS [ 8.084 s]
[INFO] GeoMesa Tools ..................................... SUCCESS [ 25.218 s]
[INFO] GeoMesa Compute .................................... SUCCESS [ 40.246 s]
[INFO] GeoMesa WPS ........................................ SUCCESS [ 4.472 s]
[INFO] GeoMesa Stream .................................... SUCCESS [ 0.012 s]
[INFO] GeoMesa Stream API ................................ SUCCESS [ 2.350 s]
[INFO] GeoMesa Stream Generic ............................. SUCCESS [ 10.005 s]
[INFO] GeoMesa Stream DataStore ........................... SUCCESS [ 15.171 s]
[INFO] GeoMesa Stream GeoServer Plugin .................... SUCCESS [ 11.295 s]
[INFO] GeoMesa Web ....................................... SUCCESS [ 0.018 s]
[INFO] GeoMesa Web Core .................................. SUCCESS [ 3.564 s]
[INFO] GeoMesa Web CSV .................................... SUCCESS [ 5.009 s]
[INFO] GeoMesa Web Data ................................... SUCCESS [ 4.068 s]
[INFO] GeoMesa Web Security .............................. SUCCESS [ 10.593 s]
[INFO] GeoMesa Assemble .................................. SUCCESS [ 11.769 s]
[INFO] GeoMesa Examples .................................. SUCCESS [ 0.012 s]
[INFO] GeoMesa Examples Accumulo Quickstart ............... SUCCESS [ 13.766 s]
[INFO] GeoMesa Examples Kafka Quickstart .................. SUCCESS [ 7.535 s]
[INFO] GeoMesa HBase Parent .............................. SUCCESS [ 0.011 s]
[INFO] GeoMesa HBase DataStore ........................... SUCCESS [ 5.790 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:16 min
[INFO] Finished at: 2015-08-07T16:57:21-06:00
[INFO] Final Memory: 211M/799M
[INFO] ------------------------------------------------------------------------
chris.snider@machine1: (Scala_GeoServer_GeoTools_VersionUpgrade)>
Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
-----Original Message-----
From: geomesa-users-bounces@xxxxxxxxxxxxxxxx [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jim Hughes
Sent: Thursday, August 06, 2015 4:17 PM
To: geomesa-users@xxxxxxxxxxxxxxxx
Subject: Re: [geomesa-users] GeoServer/GeoTools Version
Hi Chris,
Awesome. Since you aren't a LocationTech/GeoMesa committer, you'll have to fork GeoMesa and push to your fork on GitHub.
If you'd like to make a PR, you'll need to do a little paperwork.
Perhaps we can discuss that off list so that I can get all my ducks in a row.
Thanks again,
Jim
On 08/05/2015 05:41 PM, Chris Snider wrote:
> Jim,
>
> I have a local branch called Scala_GeoServer_GeoTools_VersionUpgrade that I just rebased against master. The original branch I worked from was the geomesa-1.1.0-rc.3 tag. I will rebuild locally, and try and get the tests to run, but I have been authorized
to push this back to your main repo as a branch.
>
> Chris Snider
> Senior Software Engineer
> Intelligent Software Solutions, Inc.
>
>
> -----Original Message-----
> From: geomesa-users-bounces@xxxxxxxxxxxxxxxx
> [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jim
> Hughes
> Sent: Tuesday, August 04, 2015 3:41 PM
> To: geomesa-users@xxxxxxxxxxxxxxxx
> Subject: Re: [geomesa-users] GeoServer/GeoTools Version
>
> Hi Chris,
>
> Awesome. Thanks for passing on the notes about how you got Scala and GeoTools upgraded. If you are interested in sharing your work, we're always happy to accept contributions.
>
> In terms of the license question, since GeoMesa is open-sourced through LocationTech which is part of the Eclipse Foundation, we are playing by their rules. They have a list of licenses which they consider to be open-source and business-friendly. They do
not approve the old Sun binary license used for JAI. Since the library has been used widely by the open geospatial community, LocationTech did ask for special permission, and they were rejected.
>
> The upshot is that artifacts hosted on LocationTech's Nexus server
> must not contain the JAI jars. We are allowed to provide scripts to
> download such libraries;)
>
> As a note, when the Oracle links to JAI stopped working recently, we did update our scripts to pull from an OSGeo server. That change is on master.
>
> Cheers,
>
> Jim
>
> On 08/04/2015 05:31 PM, Chris Snider wrote:
>> Jim, Chris E.,
>>
>> The SHORT story:
>>
>> I successfully compiled and deployed my updated geomesa artifacts/tools jar to my server. I ran the geomesa utils tool creating the quickstart tables in my single node Accumulo cluster. I was also able to create a Vector datastore for Accumulo using the
geomesa driver returning the data from my quickstart tables. Finally, I retrieved data and displayed in the Openlayers Preview pane using the built-in OL 3.X distributed with GeoServer.
>>
>>
>> The LONGER story:
>>
>> The reference to the install_jai from the geomesa tools fails when calling java.net as the site appears to be down. Even using the Oracle linked page at
http://www.oracle.com/technetwork/java/current-142188.html fails to return the downloadable artifact...something on Oracles side I presume.
>>
>> I was able to get GeoMesa to compile after changing the org.sprire-math dependency to sprire_2.11 version 0.10.1. This is what was throwing the error I previously sent.
>>
>> I also updated org/locationtech/geomesa/tools/repl/GeoMesaILoop.scala to comment out the "addThunk" call, but left the main body of createInterpreter as thus:
>>
>> override def createInterpreter() {
>> super.createInterpreter()
>> //addThunk {
>> intp.beQuietDuring {
>> intp.interpret(GeoMesaILoop.imports)
>> }
>> intp.beSilentDuring {
>> intp.interpret("classOf[scala.tools.jline.console.completerCompleter]") match {
>> case scala.tools.nsc.interpreter.Results.Error =>
>> println("\nWARNING: Could not load jline. For better console usability, " +
>> "run the install-jline script in $GEOMESA_HOME/bin.")
>> case _ => // ok
>> }
>> }
>> //}
>> }
>>
>> Not sure what the addThunks was supposed to do, and I can't find documentation. Several references I found to the addThunk end up in dead links back at the scala-org site.
>>
>> This let me compile to successful completion. However, I had to compile with tests turned off as several errors were thrown against the SimpleFeatureTypeBuilder from GeoTools. I deployed the updated distribution jar to my Accumulo server, but ran into issues
with the javax.media:jai-core missing classes. I had to manually download the jai_core-1.1.3 from my nexus repo (local .m2 copy) and push that to my server and restart before GeoMesa distributed multiscan would work.
>>
>> I notice this in the main pom file for gt-main
>> <dependency>
>> <groupId>org.geotools</groupId>
>> <artifactId>gt-main</artifactId>
>> <version>${gt.version}</version>
>> <exclusions>
>> <exclusion>
>> <!-- excluded due to license issues -->
>> <groupId>javax.media</groupId>
>> <artifactId>jai_core</artifactId>
>> </exclusion>
>> </exclusions>
>> </dependency>
>> Where the javax.media:jai-core is excluded with the comment about
>> license issues. What license issues are referenced? Closest license I could find is
https://java.net/projects/jai-core/sources/svn/content/trunk/LICENSE-JDL.txt?rev=111 which seems to allow for distribution of the Binary code. Alternatively, I found several references (ref:
http://stackoverflow.com/questions/1209583/using-java-advanced-imaging-with-maven) to using a different artifact that appears to have the same classes internally with <dependency>
>> <groupId>javax.media.jai</groupId>
>> <artifactId>com.springsource.javax.media.jai.core</artifactId>
>> <version>1.1.3</version>
>> </dependency>
>>
>>
>>
>> Chris Snider
>> Senior Software Engineer
>> Intelligent Software Solutions, Inc.
>>
>>
>> -----Original Message-----
>> From: geomesa-users-bounces@xxxxxxxxxxxxxxxx
>> [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jim
>> Hughes
>> Sent: Monday, August 03, 2015 3:35 PM
>> To: geomesa-users@xxxxxxxxxxxxxxxx
>> Subject: Re: [geomesa-users] GeoServer/GeoTools Version
>>
>> Hi Chris,
>>
>> Good/bad news. Updating Scala to 2.11.7 is also on the short list...
>>
>> As a quick check, have you trying blow away the org/locationtech folders in your local ~/.m2/repository? I'm wondering if Maven is dragging in an old version of the geomesa-convert libraries (which were compiled with Scala 2.10).
>>
>> If you have a branch you are willing to push to GitHub, I'm happy to pitch in and see if I notice anything obvious.
>>
>> Thanks,
>>
>> Jim
>>
>> On 08/03/2015 05:24 PM, Chris Snider wrote:
>>> Hi,
>>>
>>> I was able to update the basic Geomesa to GeoServer 2.7.1.1 and GeoTools 13.1. However, I ran into issues with the scala versions being set Our project has some dependencies for scala 2.11.2. So, I set about updating GeoMesa to scala 2.11.2.
>>>
>>> This caused a required update to the scala logging
>>> com.typesafe.scala-logging:scala-logging-slf4j_2.11 version 2.1.2 This cascaded to a required update to all the import statements for Logging and the extends Logging etc. classes. I updated all of this to the new LazyLogging in the scala-logging package.
>>> Then, I had to add the dependency for the
>>> org.scala-langmodules:scala-parser-combinators_2.11 version 1.0.4
>>>
>>> However, I am now running into an issue with the
>>> org/locationtech/geomesa/convert/SimpleFeatureConverterFactory.scala
>>> class throwing
>>> SimpleFeatureConverterFactory.scala:119: error: can't expand macros
>>> compiled by previous versions of Scala
>>>
>>> The previous error thrown like this was due to the logging. The new rendition of the error is
>>> [ERROR] reuse(i) = requiredFields(i).eval(t)
>>> [ERROR] ^
>>>
>>> So far, I have not been able to pinpoint what the underlying macro is that is being called to update an references. Any help is most appreciated.
>>>
>>> Chris Snider
>>> Senior Software Engineer
>>> Intelligent Software Solutions, Inc.
>>>
>>>
>>> -----Original Message-----
>>> From: geomesa-users-bounces@xxxxxxxxxxxxxxxx
>>> [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Chris
>>> Eichelberger
>>> Sent: Friday, July 31, 2015 11:12 AM
>>> To: Geomesa User discussions <geomesa-users@xxxxxxxxxxxxxxxx>
>>> Subject: Re: [geomesa-users] GeoServer/GeoTools Version
>>>
>>> Chris,
>>>
>>> Upgrading GeoServer and GeoTools dependencies is on our list, but we haven't gotten there yet. (Part of our intellectual property review being conducted by LocationTech will necessitate some of these upgrades).
>>>
>>> If I follow your proposal correctly, then you are talking about removing these lines (that you quote):
>>>
>>>
https://github.com/locationtech/geomesa/blob/master/geomesa-filter/s
>>> r
>>> c
>>> /main/scala/org/locationtech/geomesa/filter/_expression_/FastPropertyN
>>> a
>>> m
>>> e.scala#L45-L50
>>>
>>> Flipping through the rest of the GeoMesa source, it looks as if -- independent of the fact that GeoTools has deprecated those methods -- we may be using them elsewhere.
>>>
>>> Feel free to give this fix a try, but I suspect you would run into other build errors from some of the other GeoMesa modules. Let us know what you find!
>>>
>>> Sincerely,
>>> -- Chris
>>>
>>>
>>> On Fri, 2015-07-31 at 16:54 +0000, Chris Snider wrote:
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I grabbed the Geomesa repo and checked out the master branch. I
>>>> updated the master pom to user geoserver.version 2.7.1.1 which
>>>> requires the change to geotools.version 13.1.
>>>>
>>>>
>>>>
>>>> I tried to compile, but get errors in
>>>> org/locationtech/geomesa/filter/_expression_/FastPropertyName.scala
>>>> due to the updates in GeoTools for
>>>> theorg.geotools.filter._expression_.FilterVisitorExpressionWrapper,org.
>>>> g eotools.filter._expression_ andorg.geotools.filter.FilterVisitor
>>>>
>>>>
>>>>
>>>> The FilterVistorExpressionWrapper was removed in GeoTools 12.x with
>>>> no replacement that I have identified so far.
>>>>
>>>>
>>>>
>>>> org.geotools.filter._expression_ appears to be replaced
>>>> withorg.opengis.filter._expression_._expression_
>>>>
>>>>
>>>>
>>>> org.geotools.filter.FilterVisitor appears to be replaced
>>>> withorg.opengis.filter.FilterVisitor
>>>>
>>>>
>>>>
>>>> It looks like I should be able to remove the import
>>>> org.geotools.filter._expression_.FilterVisitorExpressionWrapper
>>>> statement then remove the block at the bottom of the class
>>>> represented by
>>>>
>>>> // geotools filter methods - deprecated but still sometimes used
>>>> override defgetType: Short = ExpressionType.ATTRIBUTE override
>>>> defgetValue(feature: SimpleFeature): AnyRef =
>>>> evaluate(feature.asInstanceOf[AnyRef])
>>>> override defevaluate(feature: SimpleFeature): AnyRef =
>>>> evaluate(feature.asInstanceOf[AnyRef])
>>>> override defaccept(visitor: FilterVisitor): Unit =
>>>> accept(newFilterVisitorExpressionWrapper(visitor),null)
>>>>
>>>>
>>>>
>>>> Does this look accurate?
>>>>
>>>>
>>>>
>>>> Chris Snider
>>>>
>>>> Senior Software Engineer
>>>>
>>>> Intelligent Software Solutions, Inc.
>>>>
>>>> Description: Description: Description:
>>>> cid:image001.png@01CA1F1F.CBC93990
>>>>
>>>>
>>>>
>>>>
>>>> From: geomesa-users-bounces@xxxxxxxxxxxxxxxx
>>>> [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Jim
>>>> Hughes
>>>> Sent: Friday, July 17, 2015 11:29 AM
>>>> To: geomesa-users@xxxxxxxxxxxxxxxx
>>>> Subject: Re: [geomesa-users] GeoServer/GeoTools Version
>>>>
>>>>
>>>>
>>>>
>>>> Chris,
>>>>
>>>> I'd definitely suggest building from master. We've made some
>>>> performance enhancements in the 1.1.0-rc.x series.
>>>>
>>>> Cheers,
>>>>
>>>> Jim
>>>>
>>>> On 07/17/2015 01:21 PM, Chris Snider wrote:
>>>>
>>>>
>>>> Jim,
>>>>
>>>>
>>>>
>>>> Should I build Geomesa from the Accumulo1.5/1.x branch, or
>>>> should I build it from Master?
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Chris Snider
>>>>
>>>> Senior Software Engineer
>>>>
>>>> Intelligent Software Solutions, Inc.
>>>>
>>>> Description: Description: Description:
>>>> cid:image001.png@01CA1F1F.CBC93990
>>>>
>>>>
>>>>
>>>>
>>>> From:geomesa-users-bounces@xxxxxxxxxxxxxxxx
>>>> [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of
>>>> Jim Hughes
>>>> Sent: Friday, July 17, 2015 11:13 AM
>>>> To: geomesa-users@xxxxxxxxxxxxxxxx
>>>> Subject: Re: [geomesa-users] GeoServer/GeoTools Version
>>>>
>>>>
>>>>
>>>>
>>>> Hi Chris,
>>>>
>>>> Yes, it should. You should just have to update the gt.version
>>>> tag in the root pom.xml to 13.1.
>>>>
>>>> I'd suggest running the unit tests; if you hit any errors,
>>>> feel free to send them along and I'll help out.
>>>>
>>>> Cheers,
>>>>
>>>> Jim
>>>>
>>>> On 07/17/2015 12:50 PM, Chris Snider wrote:
>>>>
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> Will Geomesa compile and/or run against an
>>>> installation of GeoServer 2.7.1.1 or 2.6.4 ?
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> Chris Snider
>>>>
>>>> Senior Software Engineer
>>>>
>>>> Intelligent Software Solutions, Inc.
>>>>
>>>> Description: Description: Description:
>>>> cid:image001.png@01CA1F1F.CBC93990
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> geomesa-users mailing list
>>>> geomesa-users@xxxxxxxxxxxxxxxx
>>>> To change your delivery options, retrieve your
>>>> password, or unsubscribe from this list, visit
>>>>
>>>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> geomesa-users mailing list
>>>> geomesa-users@xxxxxxxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>>
>>>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> geomesa-users mailing list
>>>> geomesa-users@xxxxxxxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or
>>>> unsubscribe from this list, visit
>>>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>>> _______________________________________________
>>> geomesa-users mailing list
>>> geomesa-users@xxxxxxxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>>> _______________________________________________
>>> geomesa-users mailing list
>>> geomesa-users@xxxxxxxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from this list, visit
>>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>> _______________________________________________
>> geomesa-users mailing list
>> geomesa-users@xxxxxxxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> http://www.locationtech.org/mailman/listinfo/geomesa-users
>> _______________________________________________
>> geomesa-users mailing list
>> geomesa-users@xxxxxxxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> http://www.locationtech.org/mailman/listinfo/geomesa-users
> _______________________________________________
> geomesa-users mailing list
> geomesa-users@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> http://www.locationtech.org/mailman/listinfo/geomesa-users
> _______________________________________________
> geomesa-users mailing list
> geomesa-users@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> http://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
