The schema and refdataset jars are only used in GeoTools and GeoServer
tests. These artifacts are not deployed as part of a GeoTools or
GeoServer release and have version numbers governed elsewhere (plus a
packager suffix) and are unrelated to GeoTools release numbers.
Deployment is a manual pr
The motivation to get into maven central probably isn't so much a "how does
this make geotools/geoserver we have right now immediately better" - I
agree, there are some awkward hoops to jump through.
I think the payout is longer term in making the artifacts easier to use and
more accessible for th
I am also bothered by this proposal as Maven Central is in my view
overly restrictive.
- What about the data-only schema jars used for app-schema testing that
are generated by downloading schemas with ant? These exist only to allow
caching of test data so tests can (once the artifacts are in th
On Wed, Mar 18, 2015 at 12:17 AM, Rich Fecher wrote:
>
> As I understood it, publishing JAI under a different group ID was in
> violation of the license. I have no claim to be the expert, and if we
> could publish under a different group ID that would be a fantastically easy
> solution. But I h
By publishing artifacts to maven central you will get some users resolving
their artifacts without OSGeo, but I don't think you will necessarily have
complete control over the order that the repositories are visited. The
caveat to that is you can make recommendations on how to structure their
setti
Thanks, I am happy to test the PR.
I think we'll be able to help test releases more in the future.
Thanks again,
Jim
On 03/17/2015 05:20 PM, Jody Garnett wrote:
I think I can clean up that pull request based on feedback, if you are
in position to test it would be good.
(Having such a long g
I think I can clean up that pull request based on feedback, if you are in
position to test it would be good.
(Having such a long gap between the beta and the release is not doing us
much good - we really need to get RC1 tested)
--
Jody Garnett
On 17 March 2015 at 10:21, Jim Hughes wrote:
> Hi
Jody,
I'm thinking of this one: https://github.com/geotools/geotools/pull/731
I tried starting a separate thread for it, but there's been a little
more traffic on the devel list today.
Cheers,
Jim
On 03/17/2015 02:26 PM, Jody Garnett wrote:
Um, which were you thinking of Jim?
--
Jody Garn
I wonder if there is a way to ask it to keep searching to the next
repository - so projects that are not concerned can download JAI from the
OSGeo repository. Like does the pom.xml with download instructions *have*
to stop searching at that point?
--
Jody Garnett
On 17 March 2015 at 13:40, Andrea
On Tue, Mar 17, 2015 at 9:40 PM, Andrea Aime
wrote:
>
> Indeed it is not foreign, but I was thinking of the situation that we had
> recently, with the OSGeo repository not keeping up with the load
> (too many concurrent connections) mostly because it is one of the first
> repos to be searched.
>
On Tue, Mar 17, 2015 at 9:05 PM, Rich Fecher wrote:
> I agree its a painful workaround. I look at it as steps in the right
> direction to maybe get someday to the point where we just can resolve
> dependencies entirely from maven central.
>
> But there perhaps may be some clarifications on the s
I agree its a painful workaround. I look at it as steps in the right
direction to maybe get someday to the point where we just can resolve
dependencies entirely from maven central.
But there perhaps may be some clarifications on the suggestion that may
alleviate concerns. I am suggesting the roo
On Tue, Mar 17, 2015 at 8:37 PM, Andrea Aime
wrote:
> On Tue, Mar 17, 2015 at 6:58 PM, Rich Fecher wrote:
>
>> Re: GeoTools on Maven Central - I just added a "Research" heading with
>> updated proposal documentation as promised.
>>
>> http://docs.codehaus.org/display/GEOTOOLS/Maven+Central
>>
>>
On Tue, Mar 17, 2015 at 6:58 PM, Rich Fecher wrote:
> Re: GeoTools on Maven Central - I just added a "Research" heading with
> updated proposal documentation as promised.
>
> http://docs.codehaus.org/display/GEOTOOLS/Maven+Central
>
> Sorry that I'm a bit later at getting around to this than I wo
I added in a note to check GeoAPI package use (may end up being a trouble
of maven central, maybe not since our artifact is distinct).
--
Jody Garnett
On 17 March 2015 at 10:58, Rich Fecher wrote:
> Re: GeoTools on Maven Central - I just added a "Research" heading with
> updated proposal docume
Um, which were you thinking of Jim?
--
Jody Garnett
On 17 March 2015 at 10:36, Jim Hughes wrote:
> Hi Jody,
>
> I just confirmed briefly: "Who != 'Bierce'" does not parse with
> ECQL.toFilter; on the other hand, "Who <> 'Bierce'" is just fine.
>
> Thanks for the merge and JIRA ticket.
>
> This
+1
On 17:38, Tue, 17 Mar 2015 Andrea Aime wrote:
> On Tue, Mar 17, 2015 at 6:31 PM, Jody Garnett
> wrote:
>
>> With CodeHaus being shut down I would like to formally move our wiki to
>> github.
>>
>
> +1
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
>
GeoTools / GeoServer Meeting 2015-03-17
===
Attending
-
Ben Caradoc-Davies
Jody Garnett
Jukka Rahkonen
Kevin Smith
Agenda
--
- CodeHaus migration
- Release: 13.0 / 2.7.0 / 1.7.0 - Travis/Jody (and Kevin)
- Online build
- Oracle
- gt-jdbc
Re: GeoTools on Maven Central - I just added a "Research" heading with
updated proposal documentation as promised.
http://docs.codehaus.org/display/GEOTOOLS/Maven+Central
Sorry that I'm a bit later at getting around to this than I would have
liked. Interested parties, please edit and provide fee
On Tue, Mar 17, 2015 at 6:31 PM, Jody Garnett
wrote:
> With CodeHaus being shut down I would like to formally move our wiki to
> github.
>
+1
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Te
Hi Jody,
I just confirmed briefly: "Who != 'Bierce'" does not parse with
ECQL.toFilter; on the other hand, "Who <> 'Bierce'" is just fine.
Thanks for the merge and JIRA ticket.
This one happens to be convenient to get into the release. I didn't
realize that your fix from the OSGeo code spri
+1.
On 18/03/15 06:31, Jody Garnett wrote:
> With CodeHaus being shut down I would like to formally move our wiki to
> github.
> --
> Jody Garnett
>
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel We
With CodeHaus being shut down I would like to formally move our wiki to
github.
--
Jody Garnett
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Sl
Hi Jim,
Well we should certainly be correct - how was it working before? Does the
parser accept both "!=" and "<>" ?
I am content to grab this pull request on to master, but this is very close.
Here is your jira ticket for the release notes:
https://jira.codehaus.org/browse/GEOT-5051
--
Jody
Hi all,
Back at the OSGeo/LocationTech code sprint, I tried out GeoMesa with
GeoTools 13.x. LocationTech is not allowing us to ship JAI, and we ran
into some issues as GeoTools tried to configure JAI logging without JAI.
Jody had submitted a PR to fix an issue when JAI is not present
(https:/
Title: Message Title
Jody Garnett created an issue
Hi all,
Last Friday, some of my fellow GeoMesans noticed that ECQL.toFilter
writes out PropertyIsNotEqual with != rather than <> (which is what the
EBNF specifies). Anyhow, Chris tossed up a PR here:
https://github.com/geotools/geotools/pull/772.
Anyhow, I wanted to start a discussion of the
Hi again,
the 2 proposals are ready:
*Views manager cleanup:*
*Proposal:*
http://docs.codehaus.org/display/GEOTOOLS/Views+Management+removal
*Associated JIRA:*
https://jira.codehaus.org/browse/GEOT-5050
*Related pull request*
https://github.com/geotools/geotools/pull/782
*JAI-EXT integration:*
Title: Message Title
Nicola Lagomarsini created an issue
On Mon, Mar 16, 2015 at 7:11 PM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:
> If you read the bottom chunk of the report you will see that part of the
> issue is that this failure does not cause the build to fail. Specifically,
> it causes the next call to JDBCTestSetup.isOnline to fai
30 matches
Mail list logo
