Ayup, the first link sets up distribution management. With that
whack, 'mvn deploy' *should* work.
To test that, I'd strongly encourage setting up a nightly job which
builds GeoGig's master branch and pushes to Nexus. Such snapshots
save on the IP review concerns and give a chance to exercise the
build and publishing. The two gotchas I've seen are (off the top of
my head):
1. Sometimes the credentials for publishing artifacts aren't
sorted. If Hudson can't publish, file a bug.
2. When setting up the job you have to click the second 'Advanced'
settings under 'Source Code Management' and click to enable 'Use
Command line git to clone'.
If you don't, you'll see an error like this:
https://hudson.locationtech.org/geomesa/job/GeoMesa%201.2/1/console
The second whack uses Jar signing. I have tried it for GeoMesa, but
I ran into problems. I believe jar signing might also seal the
jars. We have some package namespaces which are spread across
multiple jars, and that behavior seemed to clash with that.:(
In short, I hope you have better luck with jar signing!
Shout if you hit an issues; I can try and help.
On 12/02/2016 02:58 PM, Rob Emanuele
wrote:
Jim would be able to answer better, but I believe
looking at this part of their POM
And then just setting up a deployment hudson build would be
all you'd need.
You could probably copy GeoMesa's build definition (are
those export-able in hudson?) and run with that. But now I'm
just suggest work for Jim ;)
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://locationtech.org/mailman/listinfo/technology-pmc
|