[jboss-jira] [JBoss JIRA] (LOGTOOL-33) Validation of message types fails for out-of-order types

[Sanne Grinovero (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/LOGTOOL-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635929#comment-12635929 ] 

Sanne Grinovero commented on LOGTOOL-33:
----------------------------------------

Pull containing the tests:
https://github.com/jamezp/jboss-logging-tools/pull/11
                
> Validation of message types fails for out-of-order types
> --------------------------------------------------------
>
>                 Key: LOGTOOL-33
>                 URL: https://issues.jboss.org/browse/LOGTOOL-33
>             Project: Log Tool
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.CR2
>            Reporter: Sanne Grinovero
>            Assignee: David Lloyd
>
> From Infinispan:
> {code}@LogMessage(level = WARN)
> @Message(value = "Error committing cache view %2$d for cache %1$s", id = 169)
> void cacheViewCommitFailure(@Cause Exception e, String cacheName, int committedViewId);
> {code}
> {code}
> Log.java:797: Invalid format for 'Error committing cache view %2$d for cache %1$s' with parameters '[33, JBoss]'. java.util.Formatter Error: d != java.lang.String
> {code}
> I think the log message is correct, and the validator should not prevent this from being used.
> I've a test case ready in a pull request I'm sending now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira