christophe-hall / as3-commons

Automatically exported from code.google.com/p/as3-commons
0 stars 0 forks source link

2 warnings in org.as3commons #42

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Compile the reflect library and/or link to it.

3608: 'getClassLogger' has been deprecated since 2.0.  Please use 
'org.as3commons.logging.getClassLogger()'.  ClassNotFoundError.as   /as3-commons/[s
ource path] 
as3-commons-reflect-src-main-actionscript/org/as3commons/reflect/errors line 36 
Flex Problem

3608: 'getClassLogger' has been deprecated since 2.0.  Please use 
'org.as3commons.logging.getClassLogger()'.  Type.as /as3-commons/[source path] 
as3-commons-reflect-src-main-actionscript/org/as3commons/reflect    line 97 Flex 
Problem

I am using the code from the SVN, trunk version from today.

Original issue reported on code.google.com by alan...@gmail.com on 10 Feb 2011 at 12:55

GoogleCodeExporter commented 8 years ago
I have attached patched files with the warnings fixed. They are both small 
changes, marked with AG-FIX-START and AG-FIX-END comments.

Original comment by alan...@gmail.com on 10 Feb 2011 at 1:16

Attachments:

GoogleCodeExporter commented 8 years ago
Found 2 more warnings of the same type in the Bytecode library.

3608: 'getClassLogger' has been deprecated since 2.0.  Please use 
'org.as3commons.logging.getClassLogger()'.  ConstructorProxyFactory.as  /as3-commo
ns/[source path] 
as3-commons-bytecode-src-main-actionscript/org/as3commons/bytecode/proxy/impl   li
ne 46   Flex Problem

3608: 'getClassLogger' has been deprecated since 2.0.  Please use 
'org.as3commons.logging.getClassLogger()'.  ProxyFactory.as /as3-commons/[source 
path] 
as3-commons-bytecode-src-main-actionscript/org/as3commons/bytecode/proxy/impl   li
ne 123  Flex Problem

I have attached patched files for both again, changes are marked with  
AG-FIX-START and AG-FIX-END.

Original comment by alan...@gmail.com on 14 Feb 2011 at 2:16

Attachments:

GoogleCodeExporter commented 8 years ago
They indeed have been deprecated, you can get around those warnings by using 
the new methods, they are faster (performance wise) and less to write.

Original comment by mastakan...@gmail.com on 11 Sep 2011 at 6:22