clirr-devel

[Clirr-devel] working towards release 0.4

[<lak...@t-...>]

Hi guys,

Olympics are over, and I can start working on Open Source again :-)

This week I'll try to do some field testing inside my company. Assuming 
that I won't find any serious bugs my goal is to release Clirr 0.4 (both 
core and maven) next weekend.

Cheers,
Lars

Re: [Clirr-devel] working towards release 0.4

[Simon K. <si...@ec...>]

On Tue, 2004-08-31 at 16:25, Lars K=FChne wrote:
> Hi guys,
>=20
> Olympics are over, and I can start working on Open Source again :-)
>=20
> This week I'll try to do some field testing inside my company. Assuming=
=20
> that I won't find any serious bugs my goal is to release Clirr 0.4 (bot=
h=20
> core and maven) next weekend.

Great. I look forward to it.

Regards,

Simon

RE: [Clirr-devel] working towards release 0.4

[Vincent M. <vma...@pi...>]

Sounds good to me. Once it is delivered I'll do some in-house =
preaching...
:-)

Thanks
-Vincent

> -----Original Message-----
> From: cli...@li... [mailto:clirr-devel-
> ad...@li...] On Behalf Of Lars K=FChne
> Sent: mardi 31 ao=FBt 2004 06:25
> To: cli...@li...
> Subject: [Clirr-devel] working towards release 0.4
>=20
> Hi guys,
>=20
> Olympics are over, and I can start working on Open Source again :-)
>=20
> This week I'll try to do some field testing inside my company. =
Assuming
> that I won't find any serious bugs my goal is to release Clirr 0.4 =
(both
> core and maven) next weekend.
>=20
> Cheers,
> Lars
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
> _______________________________________________
> Clirr-devel mailing list
> Cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clirr-devel

Re: [Clirr-devel] working towards release 0.4

[<lak...@t-...>]

Lars Kühne wrote:

> Hi guys,
>
> Olympics are over, and I can start working on Open Source again :-)
>
> This week I'll try to do some field testing inside my company. 
> Assuming that I won't find any serious bugs my goal is to release 
> Clirr 0.4 (both core and maven) next weekend.


One of our classes at work had the following construct (simplified):


public class Example
{
    private static void method(JComponent comp)
    {
        // yes, it is possible to define a class here...
        class A1 extends MouseAdapter
        {
        }
        comp.addMouseListener(new A1());
    }
}

This results in error 1002, which means that ScopeSelector was "Unable 
to find information in class " + enclosingClass.getClassName() + " 
referring back to nested class " + jclassName"

The reason is that the compiler mangles the classname for A1 into 
Example$1A1, so the ScopeSelector gets confused by the classname 1A1 
being different from the constant name A1 in the enclosing class.

Hmmm - I'll try to figure it out tomorrow if nobody beats me to it...

Lars

Re: [Clirr-devel] working towards release 0.4

[<lak...@t-...>]

Fixed

Lars Kühne wrote:

> public class Example
> {
>    private static void method(JComponent comp)
>    {
>        // yes, it is possible to define a class here...
>        class A1 extends MouseAdapter
>        {
>        }
>        comp.addMouseListener(new A1());
>    }
> }
>
> This results in error 1002, which means that ScopeSelector was "Unable 
> to find information in class " + enclosingClass.getClassName() + " 
> referring back to nested class " + jclassName"
>
> The reason is that the compiler mangles the classname for A1 into 
> Example$1A1, so the ScopeSelector gets confused by the classname 1A1 
> being different from the constant name A1 in the enclosing class.
>
> Hmmm - I'll try to figure it out tomorrow if nobody beats me to it...

Re: [Clirr-devel] working towards release 0.4

[<lak...@t-...>]

Arghhh - not fixed!

On JDK 1.3 something seems to work differently and the unit test fails. 
So now I have a debugging session I can look forward to tomorrow morning :-)

Lars Kühne wrote:

> Fixed
>
> Lars Kühne wrote:
>
>> public class Example
>> {
>>    private static void method(JComponent comp)
>>    {
>>        // yes, it is possible to define a class here...
>>        class A1 extends MouseAdapter
>>        {
>>        }
>>        comp.addMouseListener(new A1());
>>    }
>> }
>>
>> This results in error 1002, which means that ScopeSelector was 
>> "Unable to find information in class " + 
>> enclosingClass.getClassName() + " referring back to nested class " + 
>> jclassName"
>>
>> The reason is that the compiler mangles the classname for A1 into 
>> Example$1A1, so the ScopeSelector gets confused by the classname 1A1 
>> being different from the constant name A1 in the enclosing class.
>>
>> Hmmm - I'll try to figure it out tomorrow if nobody beats me to it... 
>