You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@calcite.apache.org by Hsuan Yi Chu <hy...@maprtech.com> on 2015/07/14 02:40:54 UTC

After adding error message to CalciteResource, UtilTest.testResources fails

I added a new @BaseMessage at CalciteResource. Then, AssertionError always
pops up from UtilTest.testResources.

Do I need to register new BaseMessage to anywhere?

Thanks

Re: After adding error message to CalciteResource, UtilTest.testResources fails

Posted by Julian Hyde <jh...@apache.org>.

Glad you figured it out. The test was trying to be “helpful”.

On Jul 13, 2015, at 5:46 PM, Hsuan Yi Chu <hy...@maprtech.com> wrote:

> I figured that out.
> 
> I need to register that message to CalciteResource.properties. But note
> that the first letter needs to be capital.
> 
> Sorry for the noise...
> 
> On Mon, Jul 13, 2015 at 5:40 PM, Hsuan Yi Chu <hy...@maprtech.com> wrote:
> 
>> I added a new @BaseMessage at CalciteResource. Then, AssertionError always
>> pops up from UtilTest.testResources.
>> 
>> Do I need to register new BaseMessage to anywhere?
>> 
>> Thanks
>> 
>> 
>>

Re: After adding error message to CalciteResource, UtilTest.testResources fails

Posted by Hsuan Yi Chu <hy...@maprtech.com>.

I figured that out.

I need to register that message to CalciteResource.properties. But note
that the first letter needs to be capital.

Sorry for the noise...

On Mon, Jul 13, 2015 at 5:40 PM, Hsuan Yi Chu <hy...@maprtech.com> wrote:

> I added a new @BaseMessage at CalciteResource. Then, AssertionError always
> pops up from UtilTest.testResources.
>
> Do I need to register new BaseMessage to anywhere?
>
> Thanks
>
>
>