Trunk is currently using the components under
https://repository.jboss.org/maven2/org/jboss/mx/ -- specifically the
6.0.0.Beta1 release of each of those. The jmx/mbeans/j2se modules
formerly found Branch_5_x are not used in trunk.
I see there's a 6.0.0.Beta2 up there; seems to have been uploaded the
same day; no idea what the code differences are. It doesn't have the
JBAS-6945 fix.
If we're not ready to move to the trunk version of these components in
M2, we should find a strategy to patch 6.0.0.Beta1 to fix known
regressions from M1. I'd also need to reevaluate the check I did for
JBAS-7500 on where AS trunk stands vs what was in M1. I realize now I
compared the M1 tag's jmx/mbeans/j2se modules with the trunk version of
externalized jmx, not with the 6.0.0.Beta1 tag that AS trunk is using.
On 01/13/2010 04:34 AM, Ales Justin wrote:
> Are we going to do a new release of the org.jboss.mx artifacts
(AS is
> currently using 6.0.0.Beta1)?
Does this mean we're using our externalized JBossMX?
Afaik, we're not yet ready to switch AS to use externalized version.
*
http://lists.jboss.org/pipermail/jboss-development/2009-December/015142.html
Adrian?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss by Red Hat