search

ngageoint / geowave-vagrant

Vagrant environment for geowave development.
Apache License 2.0
5 stars 6 forks source link

Geowave building and install provisioning not working as expected #7

Open jgornowich opened 7 years ago

jgornowich commented 7 years ago

After updating the Java version and Maven wget path I am still having problems getting the vagrant provisioning to run without error. Before I can provide a possible solution I needed a little more feedback as to the underlying geowave project.

The building of the geowave jar in the provision.sh script may need updating. It looks like the GeoWaveDemoApp was moved from the deploy/ path to the examples/ path:

https://github.com/ngageoint/geowave/pull/671

Possibly the right profile to activate is now "examples-singlejar" instead of "geowave-tools-singlejar" in the maven build command?

Also, the override of the tools.finalName properties does not seem to be working as the resulting target jar after modifying the profile is "geowave-example-0.9.3-SNAPSHOT.jar". This causes the PATH_TO_JAR variable in geowave.sh script to not exist. CLASS_TO_RUN is also now in the "examples" package rather than the "datastore" package?

rfecher commented 7 years ago

I think the geowave-tools-singlejar profile used to be in the parent pom at the root of the underlying geowave project, which is the inconsistency causing the problem here.

The right thing to do is probably just use examples-singlejar, and maybe expose a variable like examples.finalName within the examples-singlejar profile.