I've noticed that modifying dependency meta-data on the head at will is common practice. What about if Messaging IS NOT compatible with AOP 2.0.0.alpha3? Shouldn't one that make this kind of changes consult with the Messaging team first? I personally haven't run any test with AOP 2.0.0.alpha3 to confirm or deny compatibility. Has anybody else done it? Thanks Ovidiu ------------------------------------------------------------------------ Subject: [jboss-cvs] repository.jboss.com/jboss/messaging/1.2.0.CR1 ... From: Thomas Diesler <thomas.diesler(a)jboss.com&gt; Date: Fri, 23 Feb 2007 17:15:31 -0500 To: jboss-cvs-commits(a)lists.jboss.org To: jboss-cvs-commits(a)lists.jboss.org User: tdiesler Date: 07/02/23 17:15:31 Modified: jboss/messaging/1.2.0.CR1 component-info.xml Log: Fix the build Revision Changes Path 1.3 +1 -0 repository.jboss.com/jboss/messaging/1.2.0.CR1/component-info.xml (In the diff below, changes in quantity of whitespace are not shown.) Index: component-info.xml =================================================================== RCS file: /cvsroot/jboss/repository.jboss.com/jboss/messaging/1.2.0.CR1/component-info.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -b -r1.2 -r1.3 --- component-info.xml 22 Feb 2007 18:47:13 -0000 1.2 +++ component-info.xml 23 Feb 2007 22:15:31 -0000 1.3 @@ -23,6 +23,7 @@ <compatible version="1.5.2.GA"/> <compatible version="1.5.3.GA"/> <compatible version="1.5.4.GA"/> + <compatible version="2.0.0.alpha3"/> </import> <import componentref="jgroups"> _______________________________________________ jboss-cvs-commits mailing list jboss-cvs-commits(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-cvs-commits