Dear Gumpmeisters,
            
The following 2 notifys should have been sent

*********************************************************** G U M P
[EMAIL PROTECTED]: Module logging-log4j-extras failed
[EMAIL PROTECTED]: Module logging-log4j-zeroconf failed
*********************************************************** G U M P
[EMAIL PROTECTED]: Module logging-log4j-extras failed
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module logging-log4j-extras has an issue affecting its community integration.
The current state of this module is 'Failed', with reason 'Update Failed'.

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-extras/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason update failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-extras/gump_work/update_logging-log4j-extras.html
Work Name: update_logging-log4j-extras (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet checkout 
http://svn.apache.org/repos/asf/logging/log4j/extras/filters/trunk 
--non-interactive logging-log4j-extras 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: URL 'http://svn.apache.org/repos/asf/logging/log4j/extras/filters/trunk' 
doesn't exist
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-log4j-extras/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-log4j-extras/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 13001604072007, vmgump.apache.org:vmgump-public:13001604072007
Gump E-mail Identifier (unique within run) #1.

*********************************************************** G U M P
[EMAIL PROTECTED]: Module logging-log4j-zeroconf failed
To whom it may engage...
        
This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Module logging-log4j-zeroconf has an issue affecting its community integration.
The current state of this module is 'Failed', with reason 'Update Failed'.

Full details are available at:
    http://vmgump.apache.org/gump/public/logging-log4j-zeroconf/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Failed with reason update failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4j-zeroconf/gump_work/update_logging-log4j-zeroconf.html
Work Name: update_logging-log4j-zeroconf (Type: Update)
Work ended in a state of : Failed
Elapsed: 
Command Line: svn --quiet checkout 
http://svn.apache.org/repos/asf/logging/companions/zeroconf/trunk 
--non-interactive logging-log4j-zeroconf 
[Working Directory: /usr/local/gump/public/workspace/cvs]
---------------------------------------------
svn: URL 'http://svn.apache.org/repos/asf/logging/companions/zeroconf/trunk' 
doesn't exist
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/logging-log4j-zeroconf/rss.xml
- Atom: http://vmgump.apache.org/gump/public/logging-log4j-zeroconf/atom.xml

============================== Gump Tracking Only ===
Produced by Gump version 2.3.
Gump Run 13001604072007, vmgump.apache.org:vmgump-public:13001604072007
Gump E-mail Identifier (unique within run) #3.


--
Apache Gump
http://gump.apache.org/ [Instance: vmgump]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to