[JBoss-dev] Microcontainer/Breakout Strategy

[Scott M Stark]

Where should the
https://svn.jboss.org/repos/jbossas/archives/trunk/aop-mc-int/ be then,
aop, mc or standalone?

I can move the container project into a separate root under
https://svn.jboss.org/repos/jbossas/projects/

-----Original Message-----
From: jboss-development-bounces at lists.jboss.org
[mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Adrian
Brock
Sent: Wednesday, August 02, 2006 8:20 PM
To: JBoss.org development list
Subject: RE: [JBoss-dev] Microcontainer/Breakout Strategy

What is the status of the microcontainer port to SVN?

If I understand correctly cvs is now read only.
Scott just created a microcontainer trunk, 
which is missing the aop integration?.

Incidently, although the container project was created as a part
of the microcontainer project, it is intended to be used by all
projects and developed independently.

It's original intention was to define the shared primitives
used by both aop and mc (as opposed to the actual integration)
but other things like the ClassInfo are obviously useful to other
projects.

The project dependencies are:
aop -> container
kernel -> container
kernel -> dependency
aop-mc-int -> container
aop-mc-int -> aop
aop-mc-int -> kernel