You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Martin Cooper <mf...@gmail.com> on 2004/11/05 20:29:27 UTC
Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
AFAIK, you shouldn't have to do the first two things for each file.
Those should just happen by default.
--
Martin Cooper
On Fri, 5 Nov 2004 19:27:30 -0000, Niall Pemberton
<ni...@blueyonder.co.uk> wrote:
> I've added a new page, but someone with with more SVN knowledge thean me
> might want to correct/update it.
>
> Niall
>
>
>
> ----- Original Message -----
> From: <de...@struts.apache.org>
> To: <de...@struts.apache.org>
> Sent: Friday, November 05, 2004 7:19 PM
> Subject: [Apache Struts Wiki] New: StrutsMaintenanceSvn
>
> Date: 2004-11-05T11:19:17
> Editor: NiallPemberton <ni...@apache.org>
> Wiki: Apache Struts Wiki
> Page: StrutsMaintenanceSvn
> URL: http://wiki.apache.org/struts/StrutsMaintenanceSvn
>
> no comment
>
> New Page:
>
> This page is intended for any useful info for SVN
>
> == Info ==
>
> * Struts Subversion [http://struts.apache.org/ repository]
> * Apache Subversion [http://www.apache.org/dev/version-control.html
> checkout instructions]
>
> == Subversion Properties ==
>
> Subversion uses properties to record meta data about files. This section
> describes the use of these properties in Struts.
>
> * '''svn:keywords''' - subversion supports keyword substitution. Need to
> set the svn:keywords property to space seprated list of the keywords and
> then add the keywords to the file.
> * '''svn:eol-style''' - determines the line ending character on a file.
>
> === Java Source Files ===
>
> When adding a new java source file the following should be set up:
>
> * set the '''svn:eol-style''' property to ''native''
> * set the '''svn:keywords''' property to ''date author id rev''
> * add the $id$ keyword in the license comments at the top of the file
> * add @version $Rev$ $Date$ to the javadoc
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Thanks Joe, good info - I've found the config file where I can set these
auto-props in TortoiseSVN
Niall
----- Original Message -----
From: "Joe Germuska" <Jo...@Germuska.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Friday, November 05, 2004 8:26 PM
Subject: Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
> At 11:29 AM -0800 11/5/04, Martin Cooper wrote:
> >AFAIK, you shouldn't have to do the first two things for each file.
> >Those should just happen by default.
>
> I'm not so sure about the defaults. I played around a little bit
> with a local SVN server and didn't see anything "on" by default, and
> I don't see anything in the online SVN book about server-side
> defaults, although maybe I just have found it yet. I think what
> "feels" like defaults may have just be side effects of the CVS
> conversion.
>
> Checking one recently added file, it doesn't seem to have any
> properties by default:
> svn proplist struts/trunk/doc/release-checklist.xml
>
> There seems to be per-user support for "runtime" defaults:
>
> "Automatic Property Setting"
> http://svnbook.red-bean.com/svnbook-1.1/ch07s02.html#svn-ch-7-sect-2.4
>
> It seems a bit sketchy that any settings there are for all subversion
> repositories; it would be kind of nice to segment them by repository
> in case different groups had different rules. For now, Struts is the
> only project I use Subversion on, so I could probably be safe using
> this facility. Are any committers besides Don using Subversion
> elsewhere?
>
> Joe
>
> --
> Joe Germuska
> Joe@Germuska.com
> http://blog.germuska.com
> "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
> back; I'll know I'm in the wrong place."
> - Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
Posted by Joe Germuska <Jo...@Germuska.com>.
At 11:29 AM -0800 11/5/04, Martin Cooper wrote:
>AFAIK, you shouldn't have to do the first two things for each file.
>Those should just happen by default.
I'm not so sure about the defaults. I played around a little bit
with a local SVN server and didn't see anything "on" by default, and
I don't see anything in the online SVN book about server-side
defaults, although maybe I just have found it yet. I think what
"feels" like defaults may have just be side effects of the CVS
conversion.
Checking one recently added file, it doesn't seem to have any
properties by default:
svn proplist struts/trunk/doc/release-checklist.xml
There seems to be per-user support for "runtime" defaults:
"Automatic Property Setting"
http://svnbook.red-bean.com/svnbook-1.1/ch07s02.html#svn-ch-7-sect-2.4
It seems a bit sketchy that any settings there are for all subversion
repositories; it would be kind of nice to segment them by repository
in case different groups had different rules. For now, Struts is the
only project I use Subversion on, so I could probably be safe using
this facility. Are any committers besides Don using Subversion
elsewhere?
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
Posted by Joe Germuska <Jo...@Germuska.com>.
At 9:41 PM +0000 11/5/04, Niall Pemberton wrote:
>It doesn't at the moment and the info Joe gave means that unless theres a
>way of configuring it on the server side then we all will have to
>indivdually configure our clients to do it.
>
>I not ice that some of the java source files have the svn:executable
>property set:
>
>http://svnbook.red-bean.com/svnbook-1.1/ch07s02.html#svn-ch-7-sect-2.3.1
>
>Do we need this or property or not - not being a unix user I deon't really
>get it, but it seems strange to set this on a source file?
Yeah, must be a side effect. There are no scripts that I can think
of in Struts which would benefit from this. It would only make sense
if we had some kind of scripts which people would run stored in CVS.
It's also not really risky or costly. I guess I'd advise (with very
weak opinion) not doing anything about it, just so to not clutter up
the SVN history with less important revisions.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
It doesn't at the moment and the info Joe gave means that unless theres a
way of configuring it on the server side then we all will have to
indivdually configure our clients to do it.
I not ice that some of the java source files have the svn:executable
property set:
http://svnbook.red-bean.com/svnbook-1.1/ch07s02.html#svn-ch-7-sect-2.3.1
Do we need this or property or not - not being a unix user I deon't really
get it, but it seems strange to set this on a source file?
Niall
----- Original Message -----
From: "Martin Cooper" <mf...@gmail.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Friday, November 05, 2004 7:29 PM
Subject: Re: [Apache Struts Wiki] New: StrutsMaintenanceSvn
> AFAIK, you shouldn't have to do the first two things for each file.
> Those should just happen by default.
>
> --
> Martin Cooper
>
>
> On Fri, 5 Nov 2004 19:27:30 -0000, Niall Pemberton
> <ni...@blueyonder.co.uk> wrote:
> > I've added a new page, but someone with with more SVN knowledge thean me
> > might want to correct/update it.
> >
> > Niall
> >
> >
> >
> > ----- Original Message -----
> > From: <de...@struts.apache.org>
> > To: <de...@struts.apache.org>
> > Sent: Friday, November 05, 2004 7:19 PM
> > Subject: [Apache Struts Wiki] New: StrutsMaintenanceSvn
> >
> > Date: 2004-11-05T11:19:17
> > Editor: NiallPemberton <ni...@apache.org>
> > Wiki: Apache Struts Wiki
> > Page: StrutsMaintenanceSvn
> > URL: http://wiki.apache.org/struts/StrutsMaintenanceSvn
> >
> > no comment
> >
> > New Page:
> >
> > This page is intended for any useful info for SVN
> >
> > == Info ==
> >
> > * Struts Subversion [http://struts.apache.org/ repository]
> > * Apache Subversion [http://www.apache.org/dev/version-control.html
> > checkout instructions]
> >
> > == Subversion Properties ==
> >
> > Subversion uses properties to record meta data about files. This section
> > describes the use of these properties in Struts.
> >
> > * '''svn:keywords''' - subversion supports keyword substitution. Need to
> > set the svn:keywords property to space seprated list of the keywords and
> > then add the keywords to the file.
> > * '''svn:eol-style''' - determines the line ending character on a file.
> >
> > === Java Source Files ===
> >
> > When adding a new java source file the following should be set up:
> >
> > * set the '''svn:eol-style''' property to ''native''
> > * set the '''svn:keywords''' property to ''date author id rev''
> > * add the $id$ keyword in the license comments at the top of the file
> > * add @version $Rev$ $Date$ to the javadoc
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org