[continuum build - FAILED - update] Mon Oct 31 08:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.08.txt


[jira] Closed: (CONTINUUM-400) Empty error message in provider email when svn not properly installed.

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-400?page=all ]
 
Emmanuel Venisse closed CONTINUUM-400:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

Fixed

 Empty error message in provider email when svn not properly installed.
 --

  Key: CONTINUUM-400
  URL: http://jira.codehaus.org/browse/CONTINUUM-400
  Project: Continuum
 Type: Improvement
 Versions: 1.0
  Environment: Windows XP
 JDK 1.5.0_04
 Reporter: Jean-Laurent de Morlhon
 Assignee: Emmanuel Venisse
 Priority: Trivial
  Fix For: 1.1



 If subversion is not properly installed (not installed at all, or imporperly 
 installed) on the machine running Continuum, and using a subversion based 
 project, the error shown in provider email is blank. No error are reported.
 Although careful reading of logs (run.sh) gives the answer.
 Build seems to continue somehow, and other exception are reported making the 
 correct error to find difficult
 Correctly installing subversion, and stopping/restarting continuum solve the 
 problem.
 Extract from log :
 ---
 253109 [Thread-2] INFO  org.apache.maven.scm.manager.ScmManager  - Command 
 line: svn --non-interactive checkout http://localhost/svn/jsftest/trunk 1
 253156 [Thread-2] WARN  org.apache.maven.continuum.scm.ContinuumScm  - Error 
 while checking out the code for project: 'jsftest', id: '1' to 
 'C:\tools\continuum-1.0\bin\win32\..\..\apps\continuum\working-directory\1'.
 253156 [Thread-2] WARN  org.apache.maven.continuum.scm.ContinuumScm  - 
 Command output: 'svn' n'est pas reconnu en tant que commande interne
 ou externe, un programme exécutable ou un fichier de commandes.
 253156 [Thread-2] WARN  org.apache.maven.continuum.scm.ContinuumScm  - 
 Provider message: The svn command failed.
 
 Extract from mail send : 
 
 Build statistics:
  State: Error
  Previous Build: No previous build.
  Started at: dim., 30 oct. 2005 19:23:38 +0100
  Finished at: dim., 30 oct. 2005 19:23:38 +0100
  Total time: 0s
  Build Trigger: Forced
  Exit code: 0
  Building machine hostname: X
  Operating system : Windows XP(Service Pack 2)
  Java version : 1.5.0_04(Sun Microsystems Inc.)
 Changes
  No files changed
 
 Build Error:
 
 -

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 09:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.09.txt


[jira] Closed: (CONTINUUM-403) cvs update with empty r argument generate error

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
 
Emmanuel Venisse closed CONTINUUM-403:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

Already fixed

 cvs update with empty r argument generate error
 ---

  Key: CONTINUUM-403
  URL: http://jira.codehaus.org/browse/CONTINUUM-403
  Project: Continuum
 Type: Bug
   Components: continuum-core
 Versions: 1.0
 Reporter: Olivier Lamy
 Assignee: Emmanuel Venisse
 Priority: Blocker
  Fix For: 1.1



 The cvs update command with an emty -r argument.
 This generate an error.
 This append when editing a project and simply updating the version of the 
 continuum project.
 The only workaround is to delete and recording again the project.
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Executing: cvs -
 f -q update -d -r
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Working director
 y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
 2005-10-31 08:00:10,363 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Error while
 updating the code for project: 'tcclient', id: '14' to 
 '/local/maven/continuum/continuum-1.0/apps/co
 ntinuum/working-directory/14' with branch/tag .
 2005-10-31 08:00:10,364 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Command outp
 ut: update: option requires an argument -- r
 Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
 [-I ign] [-W spec] [files...]
 -A  Reset any sticky tags/date/kopts.
 -P  Prune empty directories.
 -C  Overwrite locally modified files with clean repository copies.
 -d  Build directories, like checkout does.
 -f  Force a head revision match if tag/date not found.
 -l  Local directory only, no recursion.
 -R  Process directories recursively.
 -p  Send updates to standard output (avoids stickiness).
 -k kopt Use RCS kopt -k option on checkout. (is sticky)
 -r rev  Update using specified revision/tag (is sticky).
 -D date Set date to update from (is sticky).
 -j rev  Merge in changes made between current revision and rev.
 -I ign  More files to ignore (! to reset).
 -W spec Wrappers specification line.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Closed: (CONTINUUM-399) trying to build in project after a version has been checked out fails

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-399?page=all ]
 
Emmanuel Venisse closed CONTINUUM-399:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

Already fixed

 trying to build in project after a version has been checked out fails
 -

  Key: CONTINUUM-399
  URL: http://jira.codehaus.org/browse/CONTINUUM-399
  Project: Continuum
 Type: Bug
   Components: continuum-core
  Environment: Mac OS x
 Reporter: yo
 Assignee: Emmanuel Venisse
  Fix For: 1.1



 Trying to build a project for the first time works but trying to rebuild this 
 project fails after.
 2005-10-29 21:42:11,528 [SocketListener0-3] INFO  Continuum   
- Enqueuing 'AudioKit' (Build definition id=6.
 2005-10-29 21:42:12,538 [Thread-1] INFO  ContinuumScm   - 
 Updating project: id: '6', name '' with branch/tag .
 2005-10-29 21:42:12,541 [Thread-1] INFO  ScmManager - 
 Executing: svn --username *** --password  --non-interactive update -r 
 2005-10-29 21:42:12,542 [Thread-1] INFO  ScmManager - 
 Working directory: 
 /Users/***/Desktop/continuum-1.0/apps/continuum/working-directory/6
 2005-10-29 21:42:12,830 [Thread-1] WARN  ContinuumScm   - 
 Error while updating the code for project: '', id: '6' to 
 '/Users//Desktop/continuum-1.0/apps/continuum/working-directory/6' with 
 branch/tag .
 2005-10-29 21:42:12,880 [Thread-1] WARN  ContinuumScm   - 
 Command output: svn: Syntax error in revision argument ''
 2005-10-29 21:42:12,882 [Thread-1] WARN  ContinuumScm   - 
 Provider message: The svn command failed.
 2005-10-29 21:42:13,521 [Thread-1] WARN  ConfigurationService   - 
 Error reading build output for build '38'.
 java.io.FileNotFoundException: 
 /Users//Desktop/continuum-1.0/apps/continuum/build-output-directory/6/38.log.txt
  (No such file or directory)
 at java.io.FileInputStream.open(Native Method)
 at java.io.FileInputStream.init(FileInputStream.java:106)
 at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:269)
 at org.codehaus.plexus.util.FileUtils.fileRead(FileUtils.java:261)
 at 
 org.apache.maven.continuum.configuration.DefaultConfigurationService.getBuildOutput(DefaultConfigurationService.java:167)
 at 
 org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:129)
 at 
 org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96)
 at 
 org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:261)
 at 
 org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53)
 at 
 org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
 at java.lang.Thread.run(Thread.java:552)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 09:30:01 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.093001.txt


[jira] Closed: (CONTINUUM-394) encrypt password for svn repository in webview and in log file

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-394?page=all ]
 
Emmanuel Venisse closed CONTINUUM-394:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

Fixed.

 encrypt password for svn repository in webview and in log file
 --

  Key: CONTINUUM-394
  URL: http://jira.codehaus.org/browse/CONTINUUM-394
  Project: Continuum
 Type: Bug
   Components: continuum-web, continuum-core
 Versions: 1.0
  Environment: Mac Os X
 Reporter: yo
 Assignee: Emmanuel Venisse
  Fix For: 1.1



 The password for an svn repo is not hidden in the webview form and in the log 
 files. This is confidential information and should not be displayed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 10:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.10.txt


[continuum build - FAILED - update] Mon Oct 31 10:39:38 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.103938.txt


[continuum build - FAILED - update] Mon Oct 31 11:30:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.113000.txt


[continuum build - FAILED - update] Mon Oct 31 12:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.12.txt


[continuum build - FAILED - update] Mon Oct 31 13:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.13.txt


[jira] Updated: (CONTINUUM-365) add shell command execution

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-365?page=all ]

Emmanuel Venisse updated CONTINUUM-365:
---

Fix Version: (was: 1.0)
 1.1

 add shell command execution
 ---

  Key: CONTINUUM-365
  URL: http://jira.codehaus.org/browse/CONTINUUM-365
  Project: Continuum
 Type: New Feature
 Reporter: yo
  Fix For: 1.1



 add support for shell command execution and not only for shell script 
 execution.
 This way, there is no need for the dedicated ant execution and shell script 
 execution module. This can be accomplished by running a shell command and you 
 automatically added support for make, rake, ... . 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 14:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.14.txt


[continuum build - FAILED - checkout] Mon Oct 31 14:10:20 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.141020.txt


[jira] Closed: (CONTINUUM-374) TYPO: Deleting a schedule displays Are you sure you want to delete this project?

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-374?page=all ]
 
Emmanuel Venisse closed CONTINUUM-374:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

 TYPO: Deleting a schedule displays Are you sure you want to delete this 
 project?
 --

  Key: CONTINUUM-374
  URL: http://jira.codehaus.org/browse/CONTINUUM-374
  Project: Continuum
 Type: Bug
 Versions: 1.0
 Reporter: Scott Schram
 Assignee: Emmanuel Venisse
 Priority: Trivial
  Fix For: 1.1



 Deleting a schedule displays Are you sure you want to delete this project?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 14:30:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.143000.txt


[continuum build - FAILED - update] Mon Oct 31 15:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.15.txt


[continuum build - FAILED - update] Mon Oct 31 16:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.16.txt


[jira] Commented: (CONTINUUM-374) TYPO: Deleting a schedule displays Are you sure you want to delete this project?

2005-10-31 Thread Emmanuel Venisse (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-374?page=comments#action_49667 
] 

Emmanuel Venisse commented on CONTINUUM-374:


the project name is added to message

 TYPO: Deleting a schedule displays Are you sure you want to delete this 
 project?
 --

  Key: CONTINUUM-374
  URL: http://jira.codehaus.org/browse/CONTINUUM-374
  Project: Continuum
 Type: Bug
 Versions: 1.0
 Reporter: Scott Schram
 Assignee: Emmanuel Venisse
 Priority: Trivial
  Fix For: 1.1



 Deleting a schedule displays Are you sure you want to delete this project?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Commented: (CONTINUUM-321) Maven 2 properties are ignored

2005-10-31 Thread Emmanuel Venisse (JIRA)
[ http://jira.codehaus.org/browse/CONTINUUM-321?page=comments#action_49669 
] 

Emmanuel Venisse commented on CONTINUUM-321:


Is it works with 1.0?

 Maven 2 properties are ignored
 --

  Key: CONTINUUM-321
  URL: http://jira.codehaus.org/browse/CONTINUUM-321
  Project: Continuum
 Type: Bug
 Versions: 1.0-alpha-4
  Environment: Running release 1.0-alpha-4 on Linux, using Maven 2.0-beta-1 
 release
 Reporter: Bob Allison



 My Maven 2 project tree consists of a parent directory with a pom.xml and a 
 set of child projects in subdirectories of the parent directory.  In the 
 parent project, I am using a pair of properties to define the build version 
 as follows:
 project
   properties
 revision3.0/revision
 snapshot-SNAPSHOT/snapshot
   /properties
 ...
   version${revision}${snapshot}/version
 ...
 /project
 I have tried placing the properties in the parent project and in the child 
 project, but I get the same results.
 When I run the build with m2 from the command line, everything builds, 
 installs, and deploys correctly.  When the child project is built with 
 Continuum, the output from Maven looks like:
 jvm 1| 2005-09-26 13:08:13,244 [Thread-0] WARN  MavenProjectBuilder   
  -
 jvm 1|   * Using defaults for missing POM 
 qaccess:3rd-party:pom:${revision}${snapshot} *

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Closed: (CONTINUUM-402) cannot change email notifications for a user

2005-10-31 Thread Emmanuel Venisse (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-402?page=all ]
 
Emmanuel Venisse closed CONTINUUM-402:
--

  Assign To: Emmanuel Venisse
 Resolution: Fixed
Fix Version: 1.1

Done.

 cannot change email notifications for a user
 

  Key: CONTINUUM-402
  URL: http://jira.codehaus.org/browse/CONTINUUM-402
  Project: Continuum
 Type: Bug
   Components: continuum-web
 Versions: 1.0
  Environment: running on linux debian
 accessing via web from winXP
 Reporter: Adam Kiezun
 Assignee: Emmanuel Venisse
  Fix For: 1.1



 I cannot change the email notification settings so that I get notified only 
 about build failures.
 It's always 'Failure,Success' or nothing

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Mon Oct 31 17:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.17.txt


[continuum build - FAILED - update] Mon Oct 31 19:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051031.19.txt


[jira] Reopened: (CONTINUUM-403) cvs update with empty r argument generate error

2005-10-31 Thread Trygve Laugstol (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
 
Trygve Laugstol reopened CONTINUUM-403:
---


Opening to fix resolution.

 cvs update with empty r argument generate error
 ---

  Key: CONTINUUM-403
  URL: http://jira.codehaus.org/browse/CONTINUUM-403
  Project: Continuum
 Type: Bug
   Components: continuum-core
 Versions: 1.0
 Reporter: Olivier Lamy
 Assignee: Emmanuel Venisse
 Priority: Blocker
  Fix For: 1.1



 The cvs update command with an emty -r argument.
 This generate an error.
 This append when editing a project and simply updating the version of the 
 continuum project.
 The only workaround is to delete and recording again the project.
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Executing: cvs -
 f -q update -d -r
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Working director
 y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
 2005-10-31 08:00:10,363 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Error while
 updating the code for project: 'tcclient', id: '14' to 
 '/local/maven/continuum/continuum-1.0/apps/co
 ntinuum/working-directory/14' with branch/tag .
 2005-10-31 08:00:10,364 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Command outp
 ut: update: option requires an argument -- r
 Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
 [-I ign] [-W spec] [files...]
 -A  Reset any sticky tags/date/kopts.
 -P  Prune empty directories.
 -C  Overwrite locally modified files with clean repository copies.
 -d  Build directories, like checkout does.
 -f  Force a head revision match if tag/date not found.
 -l  Local directory only, no recursion.
 -R  Process directories recursively.
 -p  Send updates to standard output (avoids stickiness).
 -k kopt Use RCS kopt -k option on checkout. (is sticky)
 -r rev  Update using specified revision/tag (is sticky).
 -D date Set date to update from (is sticky).
 -j rev  Merge in changes made between current revision and rev.
 -I ign  More files to ignore (! to reset).
 -W spec Wrappers specification line.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[jira] Closed: (CONTINUUM-403) cvs update with empty r argument generate error

2005-10-31 Thread Trygve Laugstol (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-403?page=all ]
 
Trygve Laugstol closed CONTINUUM-403:
-

Resolution: Duplicate

 cvs update with empty r argument generate error
 ---

  Key: CONTINUUM-403
  URL: http://jira.codehaus.org/browse/CONTINUUM-403
  Project: Continuum
 Type: Bug
   Components: continuum-core
 Versions: 1.0
 Reporter: Olivier Lamy
 Assignee: Emmanuel Venisse
 Priority: Blocker
  Fix For: 1.1



 The cvs update command with an emty -r argument.
 This generate an error.
 This append when editing a project and simply updating the version of the 
 continuum project.
 The only workaround is to delete and recording again the project.
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Executing: cvs -
 f -q update -d -r
 2005-10-31 08:00:10,300 [Thread-1] INFO  
 org.apache.maven.scm.manager.ScmManager  - Working director
 y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14
 2005-10-31 08:00:10,363 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Error while
 updating the code for project: 'tcclient', id: '14' to 
 '/local/maven/continuum/continuum-1.0/apps/co
 ntinuum/working-directory/14' with branch/tag .
 2005-10-31 08:00:10,364 [Thread-1] WARN  
 org.apache.maven.continuum.scm.ContinuumScm  - Command outp
 ut: update: option requires an argument -- r
 Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
 [-I ign] [-W spec] [files...]
 -A  Reset any sticky tags/date/kopts.
 -P  Prune empty directories.
 -C  Overwrite locally modified files with clean repository copies.
 -d  Build directories, like checkout does.
 -f  Force a head revision match if tag/date not found.
 -l  Local directory only, no recursion.
 -R  Process directories recursively.
 -p  Send updates to standard output (avoids stickiness).
 -k kopt Use RCS kopt -k option on checkout. (is sticky)
 -r rev  Update using specified revision/tag (is sticky).
 -D date Set date to update from (is sticky).
 -j rev  Merge in changes made between current revision and rev.
 -I ign  More files to ignore (! to reset).
 -W spec Wrappers specification line.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



[continuum build - FAILED - update] Tue Nov 1 00:00:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.00.txt


[continuum build - FAILED - update] Tue Nov 1 00:30:00 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.003000.txt


[continuum build - FAILED - update] Tue Nov 1 02:00:01 GMT 2005

2005-10-31 Thread continuum
Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.020001.txt


[continuum build - SUCCESS - update] Tue Nov 1 02:30:00 GMT 2005

2005-10-31 Thread continuum
Distribution:
http://maven.zones.apache.org/~continuum/builds/continuum-20051101.023000.tar.gz

Log:
http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051101.023000.txt


[jira] Created: (CONTINUUM-406) irc notifications: support for registered nicks

2005-10-31 Thread David Blevins (JIRA)
irc notifications: support for registered nicks
---

 Key: CONTINUUM-406
 URL: http://jira.codehaus.org/browse/CONTINUUM-406
 Project: Continuum
Type: Improvement
Versions: 1.0
 Reporter: David Blevins
Priority: Minor


It seems IRC notifications don't work on irc.freenode.net.  i assume it's due 
to them removing anonymous msg'ing.

Probably need to set it up to use a registered nick, and do the /msg identify 
thing first

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira