How about this approach (I am preparing to apply it to Messaging):
The first step is to move it "in-repository", to
jbossas/projects/messaging, with history preservation and all.
Then, if this discussion ends up with the the decision to go for
separate repositories, migrate to its final repository. I assume we
won't lose history if we decide to go this way.
I need this intermediary step so I can continue development right away,
while testing the new jbossbuild-based build system for a standalone
project.
Ruel Loehr wrote:
I’m just being cautious and trying to anticipate future needs.
Ruel Loehr
JBoss QA
------------------------------------------------------------------------
*From:* jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@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(a)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(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?
--
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
jboss-development(a)lists.jboss.org <mailto:jboss-development@lists.jboss.org>
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
------------------------------------------------------------------------
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development