[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-6816) Upgrade to jboss-logging 3.1.0.CR1

Steve Ebersole (JIRA) noreply at atlassian.com
Thu Nov 10 13:45:20 EST 2011


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-6816.
-------------------------------

    Resolution: Fixed

> Upgrade to jboss-logging 3.1.0.CR1
> ----------------------------------
>
>                 Key: HHH-6816
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6816
>             Project: Hibernate Core
>          Issue Type: Task
>          Components: build, core
>    Affects Versions: 4.0.0.CR5
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.0.0.CR6
>
>          Time Spent: 11m
>
> From David:
> {{quote}}
> OK folks.  I've pushed out jboss-logging 3.1.0.CR1 and jboss-logging-tools 1.0.0.CR4.
> Here's what you need to do.
> 0. Update your dep versions (obviously)
> 1. Add the following switch to your annotation processing step (or to javac if it's combined): -AloggingVersion=3.0
> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
> 3. When you publish the POMs for artifacts built this way, you may specify jboss-logging 3.0.0.GA as the required version, and it will be compatible with such.
> Basically what you're doing with the -AloggingVersion=3.0 flag is generating larger classes in exchange for backwards compatibility.  If you develop other frameworks which are not expected to be supported on AS 7.0 (for example), you do not need this flag (logging version 3.1 is required in this case).
> {{quote}}
> We will continue to export 3.1 as the outgoing dependency.  AS can manage swapping that to 3.0 for the 7.0 builds.

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

        


More information about the hibernate-issues mailing list