On 18/05/10 14:49, Andrea Aime wrote:
> I don't think you really need permission, especially for a non core
> module.
> If it was main, renderer or something a lot of people depend onto
> I would expect some discussion before adding a dependency, but
> otherwise I don't think you really need to ask
Andrea Aime ha scritto:
> Ben Caradoc-Davies ha scritto:
>> On 18/05/10 09:22, Ben Caradoc-Davies wrote:
>>> So, if I announced that I had a third-party whizbang-1.3.2.jar that I
>>> wanted to use in app-schema testing, would I be allowed to upload it to
>>> the osgeo maven repo? I think the proces
Ben Caradoc-Davies ha scritto:
> On 18/05/10 09:22, Ben Caradoc-Davies wrote:
>> So, if I announced that I had a third-party whizbang-1.3.2.jar that I
>> wanted to use in app-schema testing, would I be allowed to upload it to
>> the osgeo maven repo? I think the process has been fairly informal so
In general we try and talk about things to see if there are areas where we
could remove duplication.
In this case I think there might be.
I am not trying to slow you down; and I really like the idea of bundling the
contents so the build goes faster. We have a couple of GML tests that are very
s
On 18/05/10 09:22, Ben Caradoc-Davies wrote:
> So, if I announced that I had a third-party whizbang-1.3.2.jar that I
> wanted to use in app-schema testing, would I be allowed to upload it to
> the osgeo maven repo? I think the process has been fairly informal so far.
In a nutshell, do I need to as
