> Either one of the options works for me (as long as whatever the underlying
> issue doesn't repeat itself)
> (And yep, the sourceforge links are fine for the same artifacts)
>
Oh that is great, means I can just checkout the tag and run locally.
I expect we are only tripping up on these beta's since we trying to release
concurrently. I will check what directory they are working in - probably
need to ensure 2.7.x is working in its own play area ...
The reason we are pulling from the maven repo instead of sourceforgs is:
> - Automated integration testing against different versions of geoserver
> (targeting N and N-1 support) on travis ( see build matrix @
> https://github.com/ngageoint/geowave/blob/master/.travis.yml ) - and
> specifically the integration testing part @ (
> https://github.com/ngageoint/geowave/blob/master/geowave-test/pom.xml#L87
> ) - basically using maven to pull down the correct war artifact per the
> build matrix settings.
>
Yeah good stuff :)
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
