[jboss-jira] [JBoss JIRA] (LOGTOOL-80) JBoss Logging 3.0.x is broken

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/LOGTOOL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated LOGTOOL-80:
---------------------------------

    Description: 
The {{org.jboss.logging.processor.generator.model.MessageLoggerImplementor}} uses {{Object[].class.getName()}} as a direct class in the code model. This generates the incorrect type when written out.

Also the implementation requires {{org.jboss.logging.DelegatingBasicLogger}} which is only in 3.1.x.

  was:The {{org.jboss.logging.processor.generator.model.MessageLoggerImplementor}} uses {{Object[].class.getName()}} as a direct class in the code model. This generates the incorrect type when written out.


    
> JBoss Logging 3.0.x is broken
> -----------------------------
>
>                 Key: LOGTOOL-80
>                 URL: https://issues.jboss.org/browse/LOGTOOL-80
>             Project: Log Tool
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: James Perkins
>            Assignee: James Perkins
>            Priority: Blocker
>             Fix For: 1.2.0.Beta2
>
>
> The {{org.jboss.logging.processor.generator.model.MessageLoggerImplementor}} uses {{Object[].class.getName()}} as a direct class in the code model. This generates the incorrect type when written out.
> Also the implementation requires {{org.jboss.logging.DelegatingBasicLogger}} which is only in 3.1.x.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira