[jboss-jira] [JBoss JIRA] Closed: (JBBUILD-68) Version Incompatibility

[Paul Gier (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBBUILD-68?page=all ]

Paul Gier closed JBBUILD-68.
----------------------------

    Resolution: Out of Date

> Version Incompatibility
> -----------------------
>
>                 Key: JBBUILD-68
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-68
>             Project: JBoss Build System
>          Issue Type: Feature Request
>            Reporter: Ryan Campbell
>
> Now that multiple standalone JBoss components will be included into the build, there is a risk that their thirdparty dependencies will diverge.  i.e., that remoting and cache will depend on incompatible versions of jgroups.  I'm putting this as a JIRA task until we are ready to discuss it in the forums.
> A basic solution would be to encode the version of the 3rd party jar that the jboss jar was compiled with in the manifest:
> jboss-remoting.jar/META-INF/MANIFEST.MF:
> JBossBuild-Compatibilities: jgroups.jar=2.2.8RC1
> So, if jboss-remoting.jar was included in a release with something besides jgroups 2.2.*, the build would produce an error.
> A fancier impl would would allow a component to define multiple comptabilities in its build file:
> <depends component="jgroups-jgroups">
>    <compatible version="2.2.*"/>
>    <compatible version="2.3.*"/>
> </depends>
> The above supports the likelihood that one version of remoting is compatible with multiple versions of jgroups.  However, its weakness is that there is an equal likelihood that remoting will at some point become incompatible with jgroups 2.2.*.  Not withstanding some mechanism to test/enforce the compatibility declaration?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira