Apache CVS (was Re: Lessons Learned)

[Richard Bair <rb...@yahoo.com>]

Thanks everyone for your insight!

Related to this, I have a question regarding the
organizational structure of CVS. I noticed that
cvs.apache.org has, predictably, a different package
for all of the top-level projects, and even
sub-projects (although all of the commons-components
are considered components and not sub-projects, hence
the lack of any of the components at this top level).
I also noticed that each of the websites is listed as
[projectname]-site.

I'm certainly not the worlds foremost expert at CVS,
so I naturally assume that since apache is laid out
this way that this must a great way to lay out a
project & its sub-projects in CVS. Is this so? What
are the pros/cons to doing it this way, as opposed to
a true tree structure? I assume it has something to do
with the way CVS does things.

Thanks again
Richard


		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org

Re: Apache CVS (was Re: Lessons Learned)

[Ian Springer <ip...@apache.org>]

Richard Bair wrote:

>>we're moving to subversion and there have been quite
>>a few discussions 
>>about the best ways of laying our repositories
>>recently. if you can use 
>>subversion, seriously consider using it. the way our
>>subversion 
>>repository is laid out is a little different.
>>
>>- robert
>>    
>>
>
>Hmm... I have been thinking about subversion.
>Collabnet is doing our hosting, so moving to
>subversion instead of cvs *shouldn't* be a big deal
>from a technical standpoint. I don't know how well
>supported subversion is via IDE's and the like. I
>assume there is a good web client for subversion as
>well?
>  
>
I know there are SVN plugins for IDEA (http://svnup.tigris.org/) and 
Eclipse (http://subclipse.tigris.org/). I've used the IDEA plugin, and 
it's pretty nice.

viewcvs (http://viewcvs.sourceforge.net/) now supports both CVS and SVN. 
This is what Apache uses - see http://svn.apache.org/viewcvs.cgi/.

If you're on a Windows system, then TortoiseSVN provides a really nice 
Windows Explorer integration - similar to TortoiseCVS.

>How is apache changing its layout for subversion? I'll
>check the archives for this list and see what is
>mentioned, are there any other good resources for
>seeing how Jakarta is going to use subversion?
>
>  
>
You can see the current layout by going to 
http://svn.apache.org/repos/asf/ in a browser.

Cheers,
Ian

>Thanks
>Richard
>
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org

Re: Apache CVS (was Re: Lessons Learned)

[Richard Bair <rb...@yahoo.com>]

> we're moving to subversion and there have been quite
> a few discussions 
> about the best ways of laying our repositories
> recently. if you can use 
> subversion, seriously consider using it. the way our
> subversion 
> repository is laid out is a little different.
> 
> - robert

Hmm... I have been thinking about subversion.
Collabnet is doing our hosting, so moving to
subversion instead of cvs *shouldn't* be a big deal
from a technical standpoint. I don't know how well
supported subversion is via IDE's and the like. I
assume there is a good web client for subversion as
well?

How is apache changing its layout for subversion? I'll
check the archives for this list and see what is
mentioned, are there any other good resources for
seeing how Jakarta is going to use subversion?

Thanks
Richard


		
__________________________________ 
Do you Yahoo!? 
Dress up your holiday email, Hollywood style. Learn more. 
http://celebrity.mail.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org

Re: Apache CVS (was Re: Lessons Learned)

[robert burrell donkin <ro...@blueyonder.co.uk>]

On 13 Dec 2004, at 22:20, Richard Bair wrote:

> Thanks everyone for your insight!
>
> Related to this, I have a question regarding the
> organizational structure of CVS. I noticed that
> cvs.apache.org has, predictably, a different package
> for all of the top-level projects, and even
> sub-projects (although all of the commons-components
> are considered components and not sub-projects, hence
> the lack of any of the components at this top level).
> I also noticed that each of the websites is listed as
> [projectname]-site.
>
> I'm certainly not the worlds foremost expert at CVS,
> so I naturally assume that since apache is laid out
> this way that this must a great way to lay out a
> project & its sub-projects in CVS. Is this so? What
> are the pros/cons to doing it this way, as opposed to
> a true tree structure? I assume it has something to do
> with the way CVS does things.

(though it is the conventional way to lay out CVS projects) i suspect 
that this organization grew rather than being planned. (though it may 
well be easier to manage permissions with this structure.)

we're moving to subversion and there have been quite a few discussions 
about the best ways of laying our repositories recently. if you can use 
subversion, seriously consider using it. the way our subversion 
repository is laid out is a little different.

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org