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
On Wed, 2006-08-02 at 19:43 -0500, Scott M Stark wrote:
Another question is integration of projects like test. This either
needs to be a binary integration, or possibly a svn link.
______________________________________________________________
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Ryan Campbell
Sent: Sunday, July 30, 2006 3:22 PM
To:
JBoss.org development list
Subject: [JBoss-dev] Microcontainer/Breakout Strategy
Now that we are in SVN, extracting a project out is just a svn
move.
The question is how do we want to do this?
Where do we want microcontainer, and further extracted
projects to go? Microcontainer is currently
under /archives/trunk, which should be marked as read only.
Ruel recommended we have a directory called projects, under
which we put extracted projects:
https://svn.jboss.org/repos/jbossas/projects/microcontainer
https://svn.jboss.org/repos/jbossas/projects/aop
https://svn.jboss.org/repos/jbossas/projects/ejb3
etc. Thoughts?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development --
xxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxx