One issue is that the mc projects (container, dependency, kernel) and
aop are now read-only in cvs, and the
https://svn.jboss.org/repos/jbossas/archives/trunk/ location. These need
to be copied from there to a writable location. Its been suggested that
such breakouts happen under a
https://svn.jboss.org/repos/jbossas/projects root:
https://svn.jboss.org/repos/jbossas/projects/microcontainer
https://svn.jboss.org/repos/jbossas/projects/aop
I need to make some changes to the vfs code in the mc container project
so I'm going to setup the
https://svn.jboss.org/repos/jbossas/projects/microcontainer. You should
do the same for aop Kabir.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Adrian Brock
Sent: Wednesday, August 02, 2006 6:39 AM
To: Kabir Khan
Cc: 'JBoss.org development list'; 'Shigeru Chiba'
Subject: [JBoss-dev] Re: AOP 2.0 alpha with dependencies
It should be 2.0.0M1 (really 2.0.0-Beta1 under the new naming
conventions)
The only problem is the MetaData integration (which also affects AOP).
i.e. use org.jboss.metadata instead of org.jboss.repository
If this is not a final release, I can live with 2.0.0-Beta1
(and aop) using the old meta data repository.
The only thing is to update the MC documentation with the
changes done in 2.0.0
On Tue, 2006-08-01 at 10:40 +0200, Kabir Khan wrote:
> Adrian:
> Do you see any problems with an MC 2.0.alpha1 at this stage? It
> probably doesn't need to be a full-blown release, just something
> tagged in cvs and available in the repository?
--
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development