The corresponding txt files in target/surefire-reports should tell you what the 
problems are with the tests. I can't tell anything just from the fact that they 
failed.

An NPE at line 129 of LogManager indicates it either couldn't set up the 
factory or the LoggerContext.  I can't tell which just from the NPE.

If you ran mvn eclipse:eclipse it has to download the artifacts because it 
isn't building them, it is just building the eclipse project files.

Ralph

On Sep 26, 2012, at 5:20 AM, Gary Gregory wrote:

> Hi All:
> 
> When I run the v2 trunk build from the command line, I get failures:
> 
> Running org.apache.logging.log4j.core.config.TestConfigurator
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.032 sec <<< 
> FAILURE!
> 
> Running org.apache.logging.log4j.core.pattern.PatternParserTest
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.362 sec <<< 
> FAILURE!
> . Actual: [20120926 07:56:11,095] INFO  [PatternParserTest        :95  ] - 
> Hello, world
> 
> If I try to run TestConfigurator from Eclipse, I get NPEs for all 4 methods 
> like:
> 
> java.lang.NullPointerException
>     at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:129)
>     at 
> org.apache.logging.log4j.core.config.TestConfigurator.testByName(TestConfigurator.java:79)
> 
> If I try to run "mvn eclipse:eclipse" to redo my project configs, I get an 
> error:
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building Log4J Core 2.0-beta2-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-core 
> ---
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.030s]
> [INFO] Log4J API ......................................... SUCCESS [0.145s]
> [INFO] Log4J Core ........................................ FAILURE [0.163s]
> [INFO] Log4J Compatibility API ........................... SKIPPED
> [INFO] SLF4J Binding ..................................... SKIPPED
> [INFO] Log4J Commons Logging ............................. SKIPPED
> [INFO] Log4J Flume NG .................................... SKIPPED
> [INFO] Log4j Web Adapters ................................ SKIPPED
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 3.850s
> [INFO] Finished at: Wed Sep 26 08:19:24 EDT 2012
> [INFO] Final Memory: 18M/219M
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default) 
> on project log4j-core: Failed to resolve dependencie
> s for one or more projects in the reactor. Reason: Missing:
> [ERROR] ----------
> [ERROR] 1) org.apache.logging.log4j:log4j-api:jar:2.0-beta2-SNAPSHOT
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=org.apache.logging.log4j 
> -DartifactId=log4j-api -Dversion=2.0-beta2-SNAPSHOT -Dpackaging=jar 
> -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the 
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j 
> -DartifactId=log4j-api -Dversion=2.0-beta2-SNAPSHOT -Dpackaging=jar 
> -Dfile=/path/to/file -Durl
> =[url] -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-beta2-SNAPSHOT
> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-beta2-SNAPSHOT
> [ERROR]
> [ERROR] ----------
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-beta2-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, 
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, 
> snapshots=false)
> [ERROR] -> [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/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn <goals> -rf :log4j-core
> 
> Why is it trying to download something it is trying to build?
> 
> Thank you,
> Gary
> 
> -- 
> E-Mail: [email protected] | [email protected] 
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory

Reply via email to