What I did was open up the type hierarchy in Eclipse and go through everything
that extended function. I think now that I have done that 1st pass (to get
"names" in there) you could do the same thing with the FunctionNameImpl
constructor - look for all occurrences in the code and check them - I
I will try to put in a shift over the weekend to update functions. Any
advice? Did you get to a certain point?
On Thu, Aug 4, 2011 at 6:34 PM, Jody Garnett wrote:
> Thanks Justin; I noted this a while back (and put in the warnings so we
> could try and detect what was going on). I think we could
Thanks Justin; I noted this a while back (and put in the warnings so we
could try and detect what was going on). I think we could remove one of the
area functions; as they both do the same thing (and less code is good).
We also have not managed to make good on your FunctionName changes yet; only
a
On Thu, Aug 4, 2011 at 1:59 PM, Andrea Aime wrote:
> On Thu, Aug 4, 2011 at 7:27 PM, Justin Deoliveira
> wrote:
> > Hi all,
> > I have recently noticed some warnings that commit from
> > DefaultFunctionFactory:
> > Aug 4, 2011 11:19:46 AM
> org.geotools.filter.function.DefaultFunctionFactory
> >
On Thu, Aug 4, 2011 at 7:27 PM, Justin Deoliveira wrote:
> Hi all,
> I have recently noticed some warnings that commit from
> DefaultFunctionFactory:
> Aug 4, 2011 11:19:46 AM org.geotools.filter.function.DefaultFunctionFactory
> loadFunctions
> WARNING: Function in10 clash between FilterFunction_
Hi all,
I have recently noticed some warnings that commit from
DefaultFunctionFactory:
Aug 4, 2011 11:19:46 AM org.geotools.filter.function.DefaultFunctionFactory
loadFunctions
WARNING: Function in10 clash between FilterFunction_in9 and
FilterFunction_in10
Aug 4, 2011 11:19:46 AM org.geotools.fil