[JBoss-dev] Microcontainer/Breakout Strategy

[Scott M Stark]

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 at lists.jboss.org
[mailto:jboss-development-bounces at 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/microcontainer>  

https://svn.jboss.org/repos/jbossas/projects/aop
<https://svn.jboss.org/repos/jbossas/projects/aop> 

https://svn.jboss.org/repos/jbossas/projects/ejb3
<https://svn.jboss.org/repos/jbossas/projects/ejb3> 

 

etc.  Thoughts?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20060731/2a55c019/attachment.html