[Anthill-pro] using two different svn repositories

[Yanko, Curtis]

This isn't uncommon in the enterprise actually. By their nature
Enterprise apps extend across group and app boundaries often times. With
a good SVN setup every subcomponent tracks it's own branches and tags so
it isn't hard to manage from that aspect either. But then, using maven
to pull in those sub component should obviate the need to build both at
the same time. That shifts the re-use model from the source code to the
component itself.
 
===
-Curt
W: 860.702.9059
M: 860.881.2050
 

________________________________

From: anthill-pro-bounces at lists.urbancode.com
[mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Steve
Boone
Sent: Friday, April 11, 2008 2:43 PM
To: AnthillPro user and support list.
Subject: Re: [Anthill-pro] using two different svn repositories


Why is the source for one project in two different repositories?  

I would think that would cause many different issues.  Generally, the
code for a project, is all stored in the same place.  That makes keeping
track of the branches, tags, etc much more reasonable and cleaner.  


On Wed, Apr 9, 2008 at 12:21 PM, emerson cargnin
<echofloripa.yell at gmail.com> wrote:


	Hi
	
	Is there any plan to allow the use of two different repository
	locations (both of the same type) in the same workflow? I'm
havin gto
	do a half deploy manually because I can't do it in one go with a
	single workflow. If i separate it into another workflow then my
deploy
	workflow (based on the first one) won't pick this up. A second
option
	would be to add a job to run a shell and run an svn co manually,
but I
	think this will end up been really complicated if I want to
enable
	branches, tags, etc to be used...
	
	thanks
	emerson
	_______________________________________________
	Anthill-pro mailing list
	Anthill-pro at lists.urbancode.com
	http://lists.urbancode.com/mailman/listinfo/anthill-pro
	




This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080414/d2ebe363/attachment-0001.htm