Dear Gumpmeisters,
            
The following 4 notifys should have been sent

*********************************************************** G U M P
[GUMP@vmgump]: Project logging-log4cxx-configure (in module logging-log4cxx) 
failed
[GUMP@vmgump]: Project apr-iconv-configure (in module apr-iconv) failed
[GUMP@vmgump]: Project james-protocols (in module james-protocols) failed
[GUMP@vmgump]: Project apacheds-dir-jdbm2 (in module apacheds) failed
*********************************************************** G U M P
[GUMP@vmgump]: Project logging-log4cxx-configure (in module logging-log4cxx) 
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 general@gump.apache.org.

Project logging-log4cxx-configure has an issue affecting its community 
integration.
This issue affects 3 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - logging-log4cxx-configure :  Apache log4cxx
    - logging-log4cxx-make :  Apache log4cxx
    - logging-log4cxx-make-install :  Apache log4cxx


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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on apr-make-install exists, no need to add for property 
--with-apr.
 -INFO- Failed with reason build failed



The following work was performed:
http://vmgump.apache.org/gump/public/logging-log4cxx/logging-log4cxx-configure/gump_work/buildscript_logging-log4cxx_logging-log4cxx-configure.html
Work Name: buildscript_logging-log4cxx_logging-log4cxx-configure (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 secs
Command Line: /srv/gump/public/workspace/logging-log4cxx/configure 
--with-apr=/srv/gump/public/workspace/apr 
--prefix=/srv/gump/public/workspace/logging-log4cxx/dest-24022012 
[Working Directory: /srv/gump/public/workspace/logging-log4cxx]
---------------------------------------------
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether make sets $(MAKE)... (cached) yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking how to run the C++ preprocessor... g++ -E
checking for doxygen... no
checking for APR... configure: error: the --with-apr parameter is incorrect. It 
must specify an install prefix, a build directory, or an apr-config file.
---------------------------------------------

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

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

*********************************************************** G U M P
[GUMP@vmgump]: Project apr-iconv-configure (in module apr-iconv) 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 general@gump.apache.org.

Project apr-iconv-configure has an issue affecting its community integration.
This issue affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - apr-iconv-configure :  Apache Portable Runtime
    - apr-iconv-make :  Apache Portable Runtime


Full details are available at:
    
http://vmgump.apache.org/gump/public/apr-iconv/apr-iconv-configure/index.html

That said, some information snippets are provided here.

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



The following work was performed:
http://vmgump.apache.org/gump/public/apr-iconv/apr-iconv-configure/gump_work/buildscript_apr-iconv_apr-iconv-configure.html
Work Name: buildscript_apr-iconv_apr-iconv-configure (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: /srv/gump/public/workspace/apr-iconv/configure 
--with-apr=/srv/gump/public/workspace/apr/dest-24022012 
--prefix=/srv/gump/public/workspace/apr-iconv/dest-24022012 
[Working Directory: /srv/gump/public/workspace/apr-iconv]
---------------------------------------------
checking for gawk... no
checking for mawk... mawk
checking for a BSD-compatible install... /usr/bin/install -c
checking for APR... configure: error: the --with-apr parameter is incorrect. It 
must specify an install prefix, a build directory, or an apr-config file.
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: 
http://vmgump.apache.org/gump/public/apr-iconv/apr-iconv-configure/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/apr-iconv/apr-iconv-configure/atom.xml

============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 05001224022012, vmgump.apache.org:vmgump:05001224022012
Gump E-mail Identifier (unique within run) #2.

*********************************************************** G U M P
[GUMP@vmgump]: Project james-protocols (in module james-protocols) 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 general@gump.apache.org.

Project james-protocols has an issue affecting its community integration.
This issue affects 2 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - james-protocols :  Apache James Protocols
    - james-protocols-test :  Apache James Protocols


Full details are available at:
    
http://vmgump.apache.org/gump/public/james-protocols/james-protocols/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/james-protocols/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/james-protocols/pom.xml
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/james-protocols/james-protocols/gump_work/build_james-protocols_james-protocols.html
Work Name: build_james-protocols_james-protocols (Type: Build)
Work ended in a state of : Failed
Elapsed: 38 secs
Command Line: /opt/maven3/bin/mvn --batch-mode -DskipTests=true --settings 
/srv/gump/public/workspace/james-protocols/gump_mvn_settings.xml package 
[Working Directory: /srv/gump/public/workspace/james-protocols]
M2_HOME: /opt/maven3
---------------------------------------------
[INFO] skip non existing resourceDirectory 
/srv/gump/public/workspace/james-protocols/pop3/src/test/resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
protocols-pop3 ---
[INFO] Compiling 12 source files to 
/srv/gump/public/workspace/james-protocols/pop3/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ protocols-pop3 ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ protocols-pop3 ---
[INFO] Building jar: 
/srv/gump/public/workspace/james-protocols/pop3/target/protocols-pop3-1.6.3-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ 
protocols-pop3 ---
[INFO] 
[INFO] --- maven-jar-plugin:2.3.2:test-jar (default) @ protocols-pop3 ---
[INFO] Building jar: 
/srv/gump/public/workspace/james-protocols/pop3/target/protocols-pop3-1.6.3-SNAPSHOT-tests.jar
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Apache James Protocols IMAP 1.6.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for 
org.apache.james:apache-james-mailbox-api:jar:0.4-SNAPSHOT is missing, no 
dependency information available
[WARNING] The POM for 
org.apache.james:apache-james-mailbox-api:jar:tests:0.4-SNAPSHOT is missing, no 
dependency information available
Downloading: 
http://localhost:8192/repo/m2-snapshot-repository/org/apache/james/apache-james-mailbox-api/0.4-SNAPSHOT/apache-james-mailbox-api-0.4-SNAPSHOT-tests.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache James Protocols ............................ SUCCESS [3.529s]
[INFO] Apache James Protocols API ........................ SUCCESS [7.661s]
[INFO] Apache James Protocols Netty Implementation ....... SUCCESS [4.495s]
[INFO] Apache James Protocols SMTP ....................... SUCCESS [9.403s]
[INFO] Apache James Protocols LMTP ....................... SUCCESS [3.480s]
[INFO] Apache James Protocols POP3 ....................... SUCCESS [3.986s]
[INFO] Apache James Protocols IMAP ....................... FAILURE [0.498s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 36.453s
[INFO] Finished at: Fri Feb 24 18:09:55 UTC 2012
[INFO] Final Memory: 43M/103M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project protocols-imap: Could not resolve 
dependencies for project 
org.apache.james.protocols:protocols-imap:jar:1.6.3-SNAPSHOT: Could not find 
artifact org.apache.james:apache-james-mailbox-api:jar:tests:0.4-SNAPSHOT in 
gump-apache.snapshots (http://localhost:8192/repo/m2-snapshot-repository) -> 
[Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :protocols-imap
---------------------------------------------

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

============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 05001224022012, vmgump.apache.org:vmgump:05001224022012
Gump E-mail Identifier (unique within run) #8.

*********************************************************** G U M P
[GUMP@vmgump]: Project apacheds-dir-jdbm2 (in module apacheds) 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 general@gump.apache.org.

Project apacheds-dir-jdbm2 has an issue affecting its community integration.
This issue affects 18 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - apacheds-all :  Apache Directory Server
    - apacheds-core-annotations :  Apache Directory Server
    - apacheds-core-annotations-test :  Apache Directory Server
    - apacheds-core-integ :  Apache Directory Server
    - apacheds-core-integ-test :  Apache Directory Server
    - apacheds-dir-jdbm2 :  Apache Directory Server
    - apacheds-jdbm-partition :  Apache Directory Server
    - apacheds-jdbm-partition-test :  Apache Directory Server
    - apacheds-kerberos-test :  Apache Directory Server
    - apacheds-ldap-client-test :  Apache Directory Server
    - apacheds-server-annotations :  Apache Directory Server
    - apacheds-server-integ :  Apache Directory Server
    - apacheds-server-integ-test :  Apache Directory Server
    - apacheds-service :  Apache Directory Server
    - apacheds-service-builder :  Apache Directory Server
    - apacheds-test-framework :  Apache Directory Server
    - apacheds-wrapper :  Apache Directory Server
    - syncrepl :  Apache Directory Server


Full details are available at:
    http://vmgump.apache.org/gump/public/apacheds/apacheds-dir-jdbm2/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -INFO- Making directory for Maven settings: 
[/srv/gump/public/workspace/apacheds/jdbm2]
 -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
/srv/gump/public/workspace/apacheds/jdbm2/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Extracted fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/apacheds/apacheds-dir-jdbm2/gump_work/build_apacheds_apacheds-dir-jdbm2.html
Work Name: build_apacheds_apacheds-dir-jdbm2 (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 secs
Command Line: /opt/maven3/bin/mvn --batch-mode --settings 
/srv/gump/public/workspace/apacheds/jdbm2/gump_mvn_settings.xml install 
[Working Directory: /srv/gump/public/workspace/apacheds/jdbm2]
M2_HOME: /opt/maven3
---------------------------------------------
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.163s
[INFO] Finished at: Fri Feb 24 20:35:28 UTC 2012
[INFO] Final Memory: 2M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] The goal you specified requires a project to execute but there is no 
POM in this directory (/srv/gump/public/workspace/apacheds/jdbm2). Please 
verify you invoked Maven from the correct directory. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException
---------------------------------------------

To subscribe to this information via syndicated feeds:
- RSS: http://vmgump.apache.org/gump/public/apacheds/apacheds-dir-jdbm2/rss.xml
- Atom: 
http://vmgump.apache.org/gump/public/apacheds/apacheds-dir-jdbm2/atom.xml

============================== Gump Tracking Only ===
Produced by Apache Gump(TM) version 2.3.
Gump Run 05001224022012, vmgump.apache.org:vmgump:05001224022012
Gump E-mail Identifier (unique within run) #9.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Reply via email to