[JBoss-dev] Microcontainer/Breakout Strategy

[Ruel Loehr]

I’m just being cautious and trying to anticipate future needs.

 

Ruel Loehr

JBoss QA

 

   _____  

From: jboss-development-bounces at lists.jboss.org [mailto:jboss-development-bounces at lists.jboss.org] On Behalf Of Ovidiu Feodorov
Sent: Monday, July 31, 2006 12:19 PM
To: JBoss.org development list
Subject: Re: [JBoss-dev] Microcontainer/Breakout Strategy

 

Ruel Loehr wrote: 

Same repository:

Pros:

            We can move files from the mc project into jboss head or vice – versa at will without losing history.  We can’t do this if they are in differing repos


Once a project is separated, why would you want to move files from it back into jboss head? 




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

HYPERLINK "https://svn.jboss.org/repos/jbossas/projects/microcontainer"https://svn.jboss.org/repos/jbossas/projects/microcontainer 

HYPERLINK "https://svn.jboss.org/repos/jbossas/projects/aop"https://svn.jboss.org/repos/jbossas/projects/aop

HYPERLINK "https://svn.jboss.org/repos/jbossas/projects/ejb3"https://svn.jboss.org/repos/jbossas/projects/ejb3

 

etc.  Thoughts?

 

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 7/28/2006

 

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 7/28/2006

 





   _____  



 
_______________________________________________
jboss-development mailing list
HYPERLINK "mailto:jboss-development at lists.jboss.org"jboss-development at lists.jboss.org
HYPERLINK "https://lists.jboss.org/mailman/listinfo/jboss-development"https://lists.jboss.org/mailman/listinfo/jboss-development
  

 


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 7/28/2006



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 7/28/2006
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-development/attachments/20060731/7cf925a3/attachment.html