[jboss-jira] [JBoss JIRA] Resolved: (JBLOGGING-49) Relocate @Messages and @MessageBundle to i18n package

[David Lloyd (JIRA)]

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

David Lloyd resolved JBLOGGING-49.
----------------------------------

    Resolution: Won't Fix


In the end we unfortunately cannot do this because we require the annotations to be present at runtime, and this means that JBoss Logging would require two JARs to be usable which is not an acceptable solution.  Hopefully we can come up with some other idea though.

> Relocate @Messages and @MessageBundle to i18n package
> -----------------------------------------------------
>
>                 Key: JBLOGGING-49
>                 URL: https://issues.jboss.org/browse/JBLOGGING-49
>             Project: JBoss Logging
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.Beta4-jboss-logging
>            Reporter: Dan Allen
>            Assignee: David Lloyd
>
> The message bundle facility in JBoss Logging is generally useful. In fact, we are planning on using it as a foundation for comprehensive i18n support in Seam 3. However, developers are going to be very standoff-ish if they have to import the @Messages and @MessageBundle annotations from a logging package (org.jboss.logging). I suggest moving them to the org.jboss.i18n package, though keeping it part of the JBoss Logging project since that will remain a foundation library and to stick to 1 JAR.
> Actual:
> org.jboss.logging.Messages
> org.jboss.logging.MessageBundle
> Proposed:
> org.jboss.i18n.Messages
> org.jboss.i18n.MessageBundle
> Relocate any other types as necessary.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira