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)
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.
-Downstream app
We will eventually have some downstream RPM's that build/bundle everything,
but still getting some bits squared away - right now there are just some
internal nightlies built automatically via jenkins, so those will resolve
themselves. (probably will clean out the maven cache, though really the
hash changes should pick that up)
Thanks for running this down!
Chris
On Thu, Jan 22, 2015 at 11:58 PM, Jody Garnett <[email protected]>
wrote:
> Thanks Chris, good (and quick) testing. I post the links to the devel
> email list here before running the final deploy to source forge. I did run
> the OS X build locally and did not have any issues.
>
> So I guess we have two approaches, short list the bundles that are two big
> and I can manually remove the extra jars ... or I can try another clean
> build run.
>
> I am curious though, you are providing links to the repo - are you
> building a downstream app and grabbing these from maven? In which case only
> a clean build and deploy step will fix.
> --
> Jod
>
>
>
>
> --
> Jody Garnett
>
> On 22 January 2015 at 19:38, Chris Bennight <[email protected]> wrote:
>
>>
>> Ref:
>> http://repo.boundlessgeo.com/main/org/geoserver/web/gs-web-app/2.6.2/
>>
>> Specifically:
>>
>> http://repo.boundlessgeo.com/main/org/geoserver/web/gs-web-app/2.6.2/gs-web-app-2.6.2.jar
>>
>>
>> Image:
>> https://dl.dropboxusercontent.com/u/6649380/2.6.2-artifact.png
>>
>> In poking around the 2.7-beta artifacts (war/jar) also appear to have
>> 2.6.2 artifacts in them, and the build times are the same day ~ 30 minutes
>> apart, so looks like something may have gone funky on the build/deploy.
>>
>>
>> (Ran into the issue with some integration tests failing - race condition
>> depending on if the 2.7-beta or 2.6.2 jars load first on the classpath -
>> https://github.com/ngageoint/geowave/pull/191 )
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>
------------------------------------------------------------------------------
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
