[Proposal] Subversion configuration
Hi committers, I propose we adopt the SVN configuration from the Maven project. Right now everyone has his own config which is a pain for several reasons: - line encodings are different. For example in Jeremi's commit all the lines of XWikiMessageTool were modified even though he only touched a few lines. - expansion of @version $Id: $ - correct mime types Here's the file I propose to use: http://maven.apache.org/developers/ svn-eol-style.txt This is from http://maven.apache.org/developers/committer- environment.html If everyone agrees, please install it in your .subversion/ directory (on unix) and somewhere in your profile under Subversion/ on windows. I'll also put it up on xwiki.org Thanks -Vincent
For what purpose we need svn:keywords="Author Date Id Revision" properties?:
xwiki/trunk/web/standard/src/main/resources/hibernate.cfg.xml Name: svn:keywords + "Author Date Id Revision"
Vincent Massol wrote:
Here's the file I propose to use: http://maven.apache.org/developers/svn-eol-style.txt This is from http://maven.apache.org/developers/committer-environment.html
If everyone agrees, please install it in your .subversion/ directory (on unix) and somewhere in your profile under Subversion/ on windows. I'll also put it up on xwiki.org
-- Artem Melentyev, UralSU, CS401
On Mar 10, 2007, at 12:52 AM, Artem Melentyev wrote:
For what purpose we need svn:keywords="Author Date Id Revision" properties?:
To expand svn keywords in source files (especially the "@version $Id: $" part). Why do we need this? To be honest I'm not sure. I've always done and never questioned it so I guess now is the right time to do so... :) Pros I can think of: - it allows us to distribute sources and if someone modifies it we can know what version of the source they're using Cons I can think of: - more work, developers need to have keyword expansion set in their subversion config file (although we would need subversion config anyway for eol, mimetypes, etc) - for developers, duplicates the information in SVN. It's mostly possibly interesting for users and even then it's not sure Note: in Svn the files are stored in the repo without the expansion; it's only on checkout that the expansion happens. Thus after more thought, I'm more tempted to say we don't need them and that we should remove all the @version I've added here and then (I'll do it of course should we agree to not use keyword expansion). Thanks -Vincent
I don't really understand how this works. If on checkout $version $ is expanded, what gets commited back? $version $ or the actual number? On 3/11/07, Vincent Massol <[email protected]> wrote:
On Mar 10, 2007, at 12:52 AM, Artem Melentyev wrote:
For what purpose we need svn:keywords="Author Date Id Revision" properties?:
To expand svn keywords in source files (especially the "@version $Id: $" part). Why do we need this?
To be honest I'm not sure. I've always done and never questioned it so I guess now is the right time to do so... :)
Pros I can think of: - it allows us to distribute sources and if someone modifies it we can know what version of the source they're using
Cons I can think of: - more work, developers need to have keyword expansion set in their subversion config file (although we would need subversion config anyway for eol, mimetypes, etc) - for developers, duplicates the information in SVN. It's mostly possibly interesting for users and even then it's not sure
Note: in Svn the files are stored in the repo without the expansion; it's only on checkout that the expansion happens.
Thus after more thought, I'm more tempted to say we don't need them and that we should remove all the @version I've added here and then (I'll do it of course should we agree to not use keyword expansion).
Thanks -Vincent
On Mar 11, 2007, at 10:38 PM, Sergiu Dumitriu wrote:
I don't really understand how this works. If on checkout $version $ is expanded, what gets commited back? $version $ or the actual number?
@version $Id: $ i.e. no expansion -Vincent
On 3/11/07, Vincent Massol <[email protected]> wrote:
On Mar 10, 2007, at 12:52 AM, Artem Melentyev wrote:
For what purpose we need svn:keywords="Author Date Id Revision" properties?:
To expand svn keywords in source files (especially the "@version $Id: $" part). Why do we need this?
To be honest I'm not sure. I've always done and never questioned it so I guess now is the right time to do so... :)
Pros I can think of: - it allows us to distribute sources and if someone modifies it we can know what version of the source they're using
Cons I can think of: - more work, developers need to have keyword expansion set in their subversion config file (although we would need subversion config anyway for eol, mimetypes, etc) - for developers, duplicates the information in SVN. It's mostly possibly interesting for users and even then it's not sure
Note: in Svn the files are stored in the repo without the expansion; it's only on checkout that the expansion happens.
Thus after more thought, I'm more tempted to say we don't need them and that we should remove all the @version I've added here and then (I'll do it of course should we agree to not use keyword expansion).
Thanks -Vincent
-- You receive this message as a subscriber of the xwiki- [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/ wws
Also I don't really understand how this works, but I'll do it if it is necessary for us :-) On 3/12/07, Vincent Massol <[email protected]> wrote:
On Mar 11, 2007, at 10:38 PM, Sergiu Dumitriu wrote:
I don't really understand how this works. If on checkout $version $ is expanded, what gets commited back? $version $ or the actual number?
@version $Id: $
i.e. no expansion
-Vincent
On 3/11/07, Vincent Massol <[email protected]> wrote:
On Mar 10, 2007, at 12:52 AM, Artem Melentyev wrote:
For what purpose we need svn:keywords="Author Date Id Revision" properties?:
To expand svn keywords in source files (especially the "@version $Id: $" part). Why do we need this?
To be honest I'm not sure. I've always done and never questioned it so I guess now is the right time to do so... :)
Pros I can think of: - it allows us to distribute sources and if someone modifies it we can know what version of the source they're using
Cons I can think of: - more work, developers need to have keyword expansion set in their subversion config file (although we would need subversion config anyway for eol, mimetypes, etc) - for developers, duplicates the information in SVN. It's mostly possibly interesting for users and even then it's not sure
Note: in Svn the files are stored in the repo without the expansion; it's only on checkout that the expansion happens.
Thus after more thought, I'm more tempted to say we don't need them and that we should remove all the @version I've added here and then (I'll do it of course should we agree to not use keyword expansion).
Thanks -Vincent
-- http://purl.org/net/sergiu -- You receive this message as a subscriber of the [email protected] list. To unsubscribe: mailto:[email protected] <[email protected]> For general help: mailto:[email protected]?subject=help<[email protected]?subject=help> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
-- You receive this message as a subscriber of the [email protected] list. To unsubscribe: mailto: [email protected] For general help: mailto: [email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
participants (4)
-
Artem Melentyev -
Phung Nam -
Sergiu Dumitriu -
Vincent Massol