Cons: No
real cons that I can think of
other than if the mc project truly wanted to exist as a separate entity
Ruel Loehr
JBoss QA
-----------------------------
512-342-7840
ext 2011
Yahoo:
ruelloehr
Skype:
ruelloehr
AOL: dokoruel
From: jboss-development-bounces@lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org]
On Behalf Of Scott M
Stark
Sent: Monday, July 31,
2006 11:40
AM
To: JBoss.org
development list
Subject: RE:
[JBoss-dev]
Microcontainer/Breakout Strategy
What is the
pro/con of having these in the
same repository? The main issue with pulling everything other than the
mc is
breaking out an integration spi to allow these projects to compile.
From: jboss-development-bounces@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?