[jboss-jira] [JBoss JIRA] (AS7-1389) Log API dependencies should be included automatically in deployments

[Scott Hasse (JIRA)]

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

Scott Hasse commented on AS7-1389:
----------------------------------

We seem to be in agreement that point 1) above provides the strongest argument for explicit visibility to third party logging APIs and implementations.  So I think it makes sense to tackle that one first, and if it can't be overcome, then we don't need to spend time with any of the rest.  In that spirit, it is probably worth clarifying exactly what sort of transition I was talking about when I made my request to "Please consider re-thinking this decision moving forward.".

If we're talking about modifications to the existing EAP 6 major version, then I agree it would not be prudent to introduce a compatibility-breaking change.

However, my impression of transitions between major versions is that customers should very much expect (with minor exceptions) compatibility-breaking changes.  Specifically the notes here:

https://access.redhat.com/site/support/policy/updates/jboss_notes/

state "Red Hat's goal is to maintain compatibility across the full life cycle of a product family (e.g., EAP 5.x patches, EAP 5.x CPs, and EAP 5.x releases are in the same EAP 5 product family).".  The subtext of that, and what we have been explicitly told by every TAM I've worked with, as well as multiple support personnel and senior RedHat developers, is that between major EAP versions (e.g. 5.x -> 6.x -> 7.x) we should certainly expect compatibility-breaking changes and that even paying customers will have to deal with them.  

Even only considering the sorts of changes that are primarily developer/deployer-facing (rather than, for instance changes to the configuration management facilities), we've seen major compatibility-breaking changes during both the EAP 4.x to 5.x transition (VFS broke Spring 2 and deployment order changed in incompatible ways for instance) and EAP 5.x to 6.x (JNDI, modules implementation and many others).

It seems to me that defaulting to not exposing third-party logging APIs and implementations (especially with an easy "switch" to flip to enable visibility for those requiring it) is minor compared to many of those previous compatibility-breaking changes.  Therefore it further seems that, strictly in the context of a major version transition such as to EAP 7.x, "compatibility requirements" taken on its own does not seem to be a valid reason to drop consideration of this change.

I'm interested to understand if I've gotten something wrong with respect to expectations around major EAP versions and compatibility.  If so there would be a number of support cases I could re-address.

Regards,

Scott
                
> Log API dependencies should be included automatically in deployments
> --------------------------------------------------------------------
>
>                 Key: AS7-1389
>                 URL: https://issues.jboss.org/browse/AS7-1389
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 7.0.0.Final
>            Reporter: David Lloyd
>            Assignee: James Perkins
>             Fix For: 7.1.0.Final
>
>
> The following log APIs should be included by deployments by default:
> * {{org.slf4j}}
> * {{org.apache.commons.logging}}
> * {{org.log4j}}
> These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}.

--
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