Permalink
Please sign in to comment.
Browse files
This commit was manufactured by cvs2svn to create tag
'GROOVY_1_0_JSR_02'. git-svn-id: http://svn.codehaus.org/groovy/tags/GROOVY_1_0_JSR_02@2346 a5544e8c-8a19-0410-ba12-f9af4593a198
- Loading branch information...
Showing
with
0 additions
and 241 deletions.
- +0 −15 CVSROOT/checkoutlist
- +0 −15 CVSROOT/commitinfo
- +0 −5 CVSROOT/damagecontrol-groovy.conf
- +0 −10 CVSROOT/dctrigger.rb
- +0 −21 CVSROOT/editinfo
- +0 −83 CVSROOT/log_accum.conf
- +0 −26 CVSROOT/modules
- +0 −12 CVSROOT/notify
- +0 −13 CVSROOT/rcsinfo
- +0 −20 CVSROOT/taginfo
- +0 −21 CVSROOT/verifymsg
@@ -1,15 +0,0 @@ | ||
-# The "checkoutlist" file is used to support additional version controlled | ||
-# administrative files in $CVSROOT/CVSROOT, such as template files. | ||
-# | ||
-# The first entry on a line is a filename which will be checked out from | ||
-# the corresponding RCS file in the $CVSROOT/CVSROOT directory. | ||
-# The remainder of the line is an error message to use if the file cannot | ||
-# be checked out. | ||
-# | ||
-# File format: | ||
-# | ||
-# [<whitespace>]<filename><whitespace><error message><end-of-line> | ||
-# | ||
-# comment lines begin with '#' | ||
-passwd | ||
-log_accum.conf |
@@ -1,15 +0,0 @@ | ||
-# The "commitinfo" file is used to control pre-commit checks. | ||
-# The filter on the right is invoked with the repository and a list | ||
-# of files to check. A non-zero exit of the filter program will | ||
-# cause the commit to be aborted. | ||
-# | ||
-# The first entry on a line is a regular expression which is tested | ||
-# against the directory that the change is being committed to, relative | ||
-# to the $CVSROOT. For the first match that is found, then the remainder | ||
-# of the line is the name of the filter to run. | ||
-# | ||
-# If the repository name does not match any of the regular expressions in this | ||
-# file, the "DEFAULT" line is used, if it is specified. | ||
-# | ||
-# If the name "ALL" appears as a regular expression it is always used | ||
-# in addition to the first matching regex or "DEFAULT". |
@@ -1,5 +0,0 @@ | ||
-project_name: Groovy | ||
-scm_spec: ":ext:dcontrol@localhost:/home/projects/groovy/scm:groovy/groovy-core" | ||
-build_command_line: "maven dc" | ||
-nag_email: groovy-dev@groovy.codehaus.org | ||
-... |
@@ -1,10 +0,0 @@ | ||
-require 'xmlrpc/client' | ||
- | ||
-url = ARGV[0] | ||
-project_name = ARGV[1] | ||
- | ||
-puts "Nudging DamageControl on #{url} to build project #{project_name}" | ||
-client = XMLRPC::Client.new2(url) | ||
-build = client.proxy("build") | ||
-result = build.trig(project_name, Time.now.utc.strftime("%Y%m%d%H%M%S")) | ||
-puts result |
@@ -1,21 +0,0 @@ | ||
-# The "editinfo" file is used to allow verification of logging | ||
-# information. It works best when a template (as specified in the | ||
-# rcsinfo file) is provided for the logging procedure. Given a | ||
-# template with locations for, a bug-id number, a list of people who | ||
-# reviewed the code before it can be checked in, and an external | ||
-# process to catalog the differences that were code reviewed, the | ||
-# following test can be applied to the code: | ||
-# | ||
-# Making sure that the entered bug-id number is correct. | ||
-# Validating that the code that was reviewed is indeed the code being | ||
-# checked in (using the bug-id number or a seperate review | ||
-# number to identify this particular code set.). | ||
-# | ||
-# If any of the above test failed, then the commit would be aborted. | ||
-# | ||
-# Actions such as mailing a copy of the report to each reviewer are | ||
-# better handled by an entry in the loginfo file. | ||
-# | ||
-# One thing that should be noted is the the ALL keyword is not | ||
-# supported. There can be only one entry that matches a given | ||
-# repository. |
@@ -1,83 +0,0 @@ | ||
-# The "log_accum.conf" file overrides the the defaults hard-coded in | ||
-# the "log_accum.pl" script allowing admins to setup the log_accum.pl | ||
-# once as executable, but not writable. Each project can then have | ||
-# it's own "log_accum.conf" to configure the behaviour of their own | ||
-# cvs commit messages. | ||
- | ||
- | ||
-# MAIL TO | ||
-# | ||
-# When set, specifies the email address(es) to | ||
-# receive commit messages. When left unset, the | ||
-# script will attempt to guess the correct | ||
-# mailing list using the repository name and | ||
-# the MLISTHOST option. | ||
-# | ||
-MAIL_TO = scm@groovy.codehaus.org | ||
- | ||
-# MAIL FROM | ||
-# | ||
-# When set, specifies the email address that | ||
-# all commit messages will be sent from. | ||
-# Very usefull for setting up a "no reply" | ||
-# address for commit messages. | ||
-# | ||
-# When not set, the script will guess the sender's | ||
-# address by prefixing the cvs user's name to the | ||
-# MLISTHOST option. | ||
-# | ||
-#MAIL_FROM = noreply@codehaus.org | ||
- | ||
-# MAIL HOST ADDRESS | ||
-# | ||
-# The host address to use when guessing either | ||
-# the TO or FROM addresses. | ||
-#MLISTHOST = codehaus.org | ||
- | ||
-# X-SENDER EMAIL HEADER | ||
-# | ||
-# When specified, adds an X-Sender header to the | ||
-# emails sent so that users can use it to more | ||
-# easily filter out cvs messages. This is very | ||
-# nice for when there is no mailing list | ||
-# dedicated to cvs commit messages. | ||
-# | ||
-XSENDER = Groovy-CVS | ||
- | ||
-# REPLY-TO EMAIL ADDRESS | ||
-# | ||
-# When REPLYTO is set an SMTP "Reply-To" email | ||
-# header will be added. This is very useful | ||
-# for keeping development discussion on a | ||
-# dev list even when cvs messages go a cvs list. | ||
-# | ||
-REPLYTO = dev@groovy.codehaus.org | ||
- | ||
-# SUBJECT PREFIX | ||
-# | ||
-# This text, plus a space, will be prepended | ||
-# to the subject line of the commit message. | ||
-# When the option specified with no value, no | ||
-# prefix will be used. | ||
-# | ||
-SUBJECT_PREFIX = | ||
- | ||
-# MESSAGE SIZE LIMIT | ||
-# | ||
-# If the delta info exceeds this threshold, no diff will be | ||
-# mailed/logged; as a replacement for this, URLs pointing | ||
-# to the corresponding ViewCVS diffs will be constructed and | ||
-# included in the mail/log message. | ||
-# | ||
-# 0 = no treshold, unlimited diffs | ||
-# x = maximum size of the diff in kb | ||
-# | ||
-#SIZELIMIT = 100; | ||
- | ||
-# VIEWCVS URL | ||
-# | ||
-# Specify here the URL to ViewCVS (without trailing slash!) | ||
-# If left unset, the script will attempt to guess the correct | ||
-# value. | ||
-# | ||
-VIEWCVS = "http://cvs.groovy.codehaus.org/groovy"; |
@@ -1,26 +0,0 @@ | ||
-# Three different line formats are valid: | ||
-# key -a aliases... | ||
-# key [options] directory | ||
-# key [options] directory files... | ||
-# | ||
-# Where "options" are composed of: | ||
-# -i prog Run "prog" on "cvs commit" from top-level of module. | ||
-# -o prog Run "prog" on "cvs checkout" of module. | ||
-# -e prog Run "prog" on "cvs export" of module. | ||
-# -t prog Run "prog" on "cvs rtag" of module. | ||
-# -u prog Run "prog" on "cvs update" of module. | ||
-# -d dir Place module in directory "dir" instead of module name. | ||
-# -l Top-level directory only -- do not recurse. | ||
-# | ||
-# NOTE: If you change any of the "Run" options above, you'll have to | ||
-# release and re-checkout any working directories of these modules. | ||
-# | ||
-# And "directory" is a path to a directory relative to $CVSROOT. | ||
-# | ||
-# The "-a" option specifies an alias. An alias is interpreted as if | ||
-# everything on the right of the "-a" had been typed on the command line. | ||
-# | ||
-# You can encode a module within a module by using the special '&' | ||
-# character to interpose another module into the current module. This | ||
-# can be useful for creating a module that consists of many directories | ||
-# spread out over the entire source repository. |
@@ -1,12 +0,0 @@ | ||
-# The "notify" file controls where notifications from watches set by | ||
-# "cvs watch add" or "cvs edit" are sent. The first entry on a line is | ||
-# a regular expression which is tested against the directory that the | ||
-# change is being made to, relative to the $CVSROOT. If it matches, | ||
-# then the remainder of the line is a filter program that should contain | ||
-# one occurrence of %s for the user to notify, and information on its | ||
-# standard input. | ||
-# | ||
-# "ALL" or "DEFAULT" can be used in place of the regular expression. | ||
-# | ||
-# For example: | ||
-#ALL mail -s "CVS notification" %s |
@@ -1,13 +0,0 @@ | ||
-# The "rcsinfo" file is used to control templates with which the editor | ||
-# is invoked on commit and import. | ||
-# | ||
-# The first entry on a line is a regular expression which is tested | ||
-# against the directory that the change is being made to, relative to the | ||
-# $CVSROOT. For the first match that is found, then the remainder of the | ||
-# line is the name of the file that contains the template. | ||
-# | ||
-# If the repository name does not match any of the regular expressions in this | ||
-# file, the "DEFAULT" line is used, if it is specified. | ||
-# | ||
-# If the name "ALL" appears as a regular expression it is always used | ||
-# in addition to the first matching regex or "DEFAULT". |
@@ -1,20 +0,0 @@ | ||
-# The "taginfo" file is used to control pre-tag checks. | ||
-# The filter on the right is invoked with the following arguments: | ||
-# | ||
-# $1 -- tagname | ||
-# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d | ||
-# $3 -- repository | ||
-# $4-> file revision [file revision ...] | ||
-# | ||
-# A non-zero exit of the filter program will cause the tag to be aborted. | ||
-# | ||
-# The first entry on a line is a regular expression which is tested | ||
-# against the directory that the change is being committed to, relative | ||
-# to the $CVSROOT. For the first match that is found, then the remainder | ||
-# of the line is the name of the filter to run. | ||
-# | ||
-# If the repository name does not match any of the regular expressions in this | ||
-# file, the "DEFAULT" line is used, if it is specified. | ||
-# | ||
-# If the name "ALL" appears as a regular expression it is always used | ||
-# in addition to the first matching regex or "DEFAULT". |
@@ -1,21 +0,0 @@ | ||
-# The "verifymsg" file is used to allow verification of logging | ||
-# information. It works best when a template (as specified in the | ||
-# rcsinfo file) is provided for the logging procedure. Given a | ||
-# template with locations for, a bug-id number, a list of people who | ||
-# reviewed the code before it can be checked in, and an external | ||
-# process to catalog the differences that were code reviewed, the | ||
-# following test can be applied to the code: | ||
-# | ||
-# Making sure that the entered bug-id number is correct. | ||
-# Validating that the code that was reviewed is indeed the code being | ||
-# checked in (using the bug-id number or a seperate review | ||
-# number to identify this particular code set.). | ||
-# | ||
-# If any of the above test failed, then the commit would be aborted. | ||
-# | ||
-# Actions such as mailing a copy of the report to each reviewer are | ||
-# better handled by an entry in the loginfo file. | ||
-# | ||
-# One thing that should be noted is the the ALL keyword is not | ||
-# supported. There can be only one entry that matches a given | ||
-# repository. |
0 comments on commit
5ebdc6c