Re: Subversion

[Ate Douma]

My client has decided to switch over to subversion, regardless the state 
of subclipse for exactly the reason you indicated (it was my proposal): 
version history on moved files and also easier support for refactorings. 
Subclipse will catch up eventually, I'm sure of it. For the time being, 
for so far subclipse isn't working as needed, command line access or one 
of the other client tools will have to do.

I must note though we are *not* yet using subversion, but within weeks
we will. Whatever issues we have which may be of interest to portals I 
will share of course.

Regards,
Ate
David Sean Taylor wrote:
We need to move the CVS out of Jakarta and into Portals.
This leads me again to the question I've asked before.
Is this a good time to migrate (both J1 and J2) to Subversion?
 From what I hear, Apache will be migrating all repositories to 
Subversion within the next year, regardless.

Im wondering if the time is right now.
As you are probably aware, Scott is working on a major refactoring, 
moving many package subtrees out of the portal subproject and into their 
respective components/ subprojects.
The big problem I see with this, and it has nothing to do with Scott's 
refactoring, which I fully support, is that we will lose version history 
on all moved files!

With Subversion, this will not happen. Subversion works very well with 
keeping history when files are moved during refactoring.

The one issue that has been raised often is that Eclipse does not 
integrate with Subversion.
We need to find that one out for ourselves.
Download Subclipse

http://subclipse.tigris.org/
and try it. I plan to next week.
Look forward to your comments
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]