Developers List
Subject: Re: Migrate to SVN?
I remain unenthused by SVN, probably because I don't have to manage a
CVS
server. Effectively I'm -1, but I'm probably not going to fight.
My main reason is that SVN does not appear to be that widely adopted
yet. A
sign that the time has come to migrate
[mailto:[EMAIL PROTECTED]
Sent: Friday, November 26, 2004 6:13 PM
To: Jakarta Commons Developers List
Subject: Re: Migrate to SVN?
I remain unenthused by SVN, probably because I don't have to manage a
CVS
server. Effectively I'm -1, but I'm probably not going to fight.
My main reason
to get work done.
Gary
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Friday, November 26, 2004 3:13 PM
To: Jakarta Commons Developers List
Subject: Re: Migrate to SVN?
I remain unenthused by SVN, probably because I don't have to manage a
CVS
server
and is a disincentive for me. Yes, playing with a new toy
would be fun but at the end of the day, I need to get work done.
Gary
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Friday, November 26, 2004 3:13 PM
To: Jakarta Commons Developers List
Subject: Re: Migrate
On 29 Nov 2004, at 14:15, Shapira, Yoav wrote:
Hi,
I feel the same as Senor Colebourne to a large extent. Not -1, but not
a +1 either -- a true neutral 0 on this one.
When we do move, we need to make sure the relevant documentation for
potential contributors, e.g.
: Migrate to SVN?
On 29 Nov 2004, at 14:15, Shapira, Yoav wrote:
Hi,
I feel the same as Senor Colebourne to a large extent. Not -1, but
not
a +1 either -- a true neutral 0 on this one.
When we do move, we need to make sure the relevant documentation for
potential contributors, e.g.
http
I doubt Eclipse will ever have built-in svn support because there are
several third party plugins available. Since adding a plugin
update site
is so trivial in Eclipse I wouldn't think this would be a big deal.
The plugin I use with Struts svn is http://subclipse.tigris.org/. It
works
On Tue, 30 Nov 2004 09:31:25 +1300, Sharples, Colin
[EMAIL PROTECTED] wrote:
I doubt Eclipse will ever have built-in svn support because there are
several third party plugins available. Since adding a plugin
update site
is so trivial in Eclipse I wouldn't think this would be a big deal.
I'm working with subversion (1.1.1)/subclipse/tortoiseSVN for a while now and
I'm not completely convinced.
The subclipse plugin for eclipse is by far not as mature as the cvs support (no
links supported etc.)
I was a little bit disappointed when I tried to use subclipse behind a proxy. I
Le 26 nov. 04, à 00:07, Brett Porter a écrit :
Has anyone experienced maven's svn support ?
The scm plugin is probably the only thing not supporting it, and
that's just a
time issue. If it were a priority, it could be done reasonably quickly.
Well, for Maven-based webistes (all at commons) that
I don't have any problems with moving to SVN, in fact I've been itching
to use it for a while, since it's become relatively mature. The only
things I am unsure about is the tool support - I find the advanced CVS
support in Eclipse invaluable. However, I guess the more people that use
SVN, the
Well, for Maven-based webistes (all at commons) that seems to be quite
an issue.
Is there any other place than the scm plugin where svn integration in
maven makes sense ?
The scm plugin is only used for checkout, tagging, releases, etc.
The changelog and activity reports work just fine in SVN.
+1
Noel J. Bergman wrote:
6) should I just delete the /jakarta-commons-sandbox/email directory, or
leave the folder and a note pointing to the promotion? What about the
website as well? I think for [configuration] we just deleted both.
The ideal scenario would be to use cvs delete on
Henri Yandell wrote:
We've started doing Jakarta projects over to SVN, but we've been doing
the easy stuff first to get into the hang of it.
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year;
So Henri you mean like in ~ 2006? This is really far out. Can't
The IDEAL situation would be to convert Jakarta Commons to SVN. Can we
PLEASE consider doing so?
A lot of projects, including the HTTP Server project, have been
migrating,
as can be seen from http://svn.apache.org/viewcvs. Jakarta and XML are
definitely the laggards now.
--- Noel
+1
If the
The IDEAL situation would be to convert Jakarta Commons to SVN. Can
we
PLEASE consider doing so?
+1 to migrate all at one time
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The IDEAL situation would be to convert Jakarta Commons to SVN.
Can we
PLEASE consider doing so?
+1 to migrate all at one time
From the point of VFS (for sure, only a commons sandbox) +1
-
To unsubscribe, e-mail: [EMAIL
+1 from me as well -- seems to make sense to move as a group.
Phil
Alex Karasulu wrote:
+1
Noel J. Bergman wrote:
6) should I just delete the /jakarta-commons-sandbox/email
directory, or
leave the folder and a note pointing to the promotion? What about the
website as well? I think for
I remain unenthused by SVN, probably because I don't have to manage a CVS
server. Effectively I'm -1, but I'm probably not going to fight.
My main reason is that SVN does not appear to be that widely adopted yet. A
sign that the time has come to migrate would be when Eclipse/Idea ships with
SVN
Stephen Colebourne wrote:
My main reason is that SVN does not appear to be that widely adopted yet. A
sign that the time has come to migrate would be when Eclipse/Idea ships with
SVN support built in.
IDEA's current EAP cycle has included support OOTB. I haven't tried it
yet though...
At the
Noel,
Can you comment on the admin-side advantages of svn ?
I do know most of the client-side advantages...
thanks
paul
Le 27 nov. 04, à 00:12, Stephen Colebourne a écrit :
I remain unenthused by SVN, probably because I don't have to manage a
CVS
server. Effectively I'm -1, but I'm probably not
Can you comment on the admin-side advantages of svn ?
Elimination of the need for shell accounts, and the ability to shift load
from the core infrastructure team to the PMCs. Trivial project movement.
And since we sometimes have to ... cough ... help recover from people
playing around with ,v
-Original Message-
From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
Sent: Friday, November 26, 2004 11:05 PM
To: Jakarta Commons Developers List
Subject: RE: Migrate to SVN?
Can you comment on the admin-side advantages of svn ?
Elimination of the need for shell accounts, and the ability
Stephen Colebourne wrote:
I remain unenthused by SVN, probably because I don't have to manage a CVS
server. Effectively I'm -1, but I'm probably not going to fight.
My main reason is that SVN does not appear to be that widely adopted yet. A
sign that the time has come to migrate would be when
We've started doing Jakarta projects over to SVN, but we've been doing
the easy stuff first to get into the hang of it.
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year; unless there are reasons to move quicker.
One thing to work out with Commons is whether
Henri Yandell wrote:
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year; unless there are reasons to move quicker.
End of NEXT year?! I do hope you're kidding.
--- Noel
-
To
On Thu, 25 Nov 2004 14:07:39 -0500, Noel J. Bergman [EMAIL PROTECTED] wrote:
6) should I just delete the /jakarta-commons-sandbox/email directory, or
leave the folder and a note pointing to the promotion? What about the
website as well? I think for [configuration] we just deleted both.
Now, for this cvs-to-svn (whichever its name is) should be working well.
The only experience I had were pretty dark.
If someone else manages this well, I'd be happy to switch to svn as a
developer. I am using this myself already much.
Has anyone experienced maven's svn support ?
paul
Le 25 nov.
On Thu, 25 Nov 2004 15:04:37 -0500, Henri Yandell [EMAIL PROTECTED] wrote:
We've started doing Jakarta projects over to SVN, but we've been doing
the easy stuff first to get into the hang of it.
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year; unless
On Thu, 25 Nov 2004 15:13:41 -0500, Noel J. Bergman [EMAIL PROTECTED] wrote:
Henri Yandell wrote:
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year; unless there are reasons to move quicker.
End of NEXT year?! I do hope you're kidding.
All of
Henri Yandell wrote:
Noel J. Bergman wrote:
Henri Yandell wrote:
I think a pretty fair target for Jakarta is to be fully in SVN by the
end of next year; unless there are reasons to move quicker.
End of NEXT year?! I do hope you're kidding.
All of Jakarta, not just Commons.
I
It gave me pain; as has installing an svn server, client, Subclipse
(Eclipse plugin), tagging in svn and generally maintaining the Berkley
DB (it can get corrupted).
The ASF though has much more experience with the svn server-side; so
the only ones that would really worry me are installing a
On Thu, 25 Nov 2004 15:37:42 -0500, Henri Yandell [EMAIL PROTECTED] wrote:
It gave me pain; as has installing an svn server, client, Subclipse
(Eclipse plugin), tagging in svn and generally maintaining the Berkley
DB (it can get corrupted).
The ASF though has much more experience with the
Le 25 nov. 04, à 21:37, Henri Yandell a écrit :
and on the Mac you do it the same way as on Linux; the
fink install was crappy. It might be usable now, or maybe there's a
Mac package for it.
It worked fine for me, both server and client.
Do note that it is now in the stable tree, svn version
The problems I've hit are:
1/
No easy way to do 'cvs status -v project.xml' and list the tags that
have been applied to a component. Instead I've switched to using an
alias with:
svn list http://svn.osjava.org/svn/osjava/releases | grep $1 | sed 's/\/$//'
2/
Have to change the mindset for
I'm not really committing frequently in commons, but I'm in favour of this
happening.
Has anyone experienced maven's svn support ?
The scm plugin is probably the only thing not supporting it, and that's just a
time issue. If it were a priority, it could be done reasonably quickly.
Other than
36 matches
Mail list logo
