You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by de...@struts.apache.org on 2004/11/05 23:00:46 UTC

[Apache Struts Wiki] Updated: StrutsMaintenanceSvn

   Date: 2004-11-05T14:00:46
   Editor: NiallPemberton <ni...@apache.org>
   Wiki: Apache Struts Wiki
   Page: StrutsMaintenanceSvn
   URL: http://wiki.apache.org/struts/StrutsMaintenanceSvn

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -4,6 +4,7 @@
 
  * Struts Subversion [http://struts.apache.org/ repository]
  * Apache Subversion [http://www.apache.org/dev/version-control.html checkout instructions]
+ * Subversion [http://svnbook.red-bean.com/svnbook-1.1/index.html Red Book]
 
 == Subversion Properties ==
 
@@ -12,11 +13,36 @@
  * '''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 ===
+=== Configuring the Client: Automatic Property Setting ===
+
+You should be able to configure the client your using for svn to automatically set properties on newly added files. The following bits of the red book may help.
+
+ * [http://svnbook.red-bean.com/svnbook-1.1/ch07s02.html#svn-ch-7-sect-2.4 Automatic Property Setting]
+ * [http://svnbook.red-bean.com/svnbook-1.1/ch07.html#svn-ch-7-sect-1.3.2 Configuraton Options]
+
+First you need to set the '''enable-auto-props''' to ''yes''. Then in the '''auto-props''' section add properties for specified file patterns.
+
+=== Struts Subversion Property Settings ===
+
+==== 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'' 
+The new file should have the following properties:
+
+ * '''svn:eol-style''' property set to ''native'' 
+ * '''svn:keywords''' property set to ''date author id rev'' 
+
+The new file should contain the following keywords:
+
  * add the $id$ keyword in the license comments at the top of the file
  * add @version $Rev$ $Date$ to the javadoc
+
+==== Documentation ====
+
+The '''*.xml''' documentation files have the following properties set:
+
+ * '''svn:eol-style''' property set to ''native'' 
+ * '''svn:keywords''' property set to ''author date id'' 
+
+'''Note:''' not sure why were setting the svn:keywords since they aren't being used in the documents?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: [Apache Struts Wiki] Updated: StrutsMaintenanceSvn

Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Joe,

Thanks for the comments, I've removed that question from the wiki - I guess
its no big deal to leave whats been set already as the default, then if
theres ever a need to use them in the future, then the properties wouldn't
need changing.

Niall

----- Original Message ----- 
From: "Joe Germuska" <Jo...@Germuska.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Friday, November 05, 2004 10:16 PM
Subject: Re: [Apache Struts Wiki] Updated: StrutsMaintenanceSvn


> At 10:00 PM +0000 11/5/04, dev@struts.apache.org wrote:
> >+==== Documentation ====
> >+
> >+The '''*.xml''' documentation files have the following properties set:
> >+
> >+ * '''svn:eol-style''' property set to ''native''
> >+ * '''svn:keywords''' property set to ''author date id''
> >+
> >+'''Note:''' not sure why were setting the svn:keywords since they
> >aren't being used in the documents?
>
> These were on by default as a side effect of the CVS conversion.
> However, I personally think that the $Id$ property, at least, would
> be reasonably included in any XML file.  Almost any text file,
> actually, especially if it has a "comment" syntax that allows it to
> be included without disrupting the content.  I think it comes in
> handy to have that information clearly available.
>
> 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] Updated: StrutsMaintenanceSvn

Posted by Joe Germuska <Jo...@Germuska.com>.
At 10:00 PM +0000 11/5/04, dev@struts.apache.org wrote:
>+==== Documentation ====
>+
>+The '''*.xml''' documentation files have the following properties set:
>+
>+ * '''svn:eol-style''' property set to ''native''
>+ * '''svn:keywords''' property set to ''author date id''
>+
>+'''Note:''' not sure why were setting the svn:keywords since they 
>aren't being used in the documents?

These were on by default as a side effect of the CVS conversion. 
However, I personally think that the $Id$ property, at least, would 
be reasonably included in any XML file.  Almost any text file, 
actually, especially if it has a "comment" syntax that allows it to 
be included without disrupting the content.  I think it comes in 
handy to have that information clearly available.

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