Sorry this is costing you so much time. I will try to fix the other unit test tonight.
Ralph On Sep 26, 2012, at 2:16 PM, Gary Gregory wrote: > Ah! I RTFM'd the error, which pointed me to Maven's -U option, which let me > proceed... until: > > [INFO] --- maven-bundle-plugin:2.3.7:manifest (bundle-manifest) @ > log4j-flume-ng --- > [ERROR] Manifest > org.apache.logging.log4j.adapters:log4j-flume-ng:jar:2.0-beta2-SNAPSHOT : The > default package '.' is not permitted by the Import-Package syntax > . > This can be caused by compile errors in Eclipse because Eclipse creates > valid class files regardless of compile errors. > The following package(s) import from the default package > [org.apache.logging.log4j.flume.appender] > [ERROR] Error(s) found in manifest configuration > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Log4j 2 .................................... SUCCESS [1.390s] > [INFO] Log4J API ......................................... SUCCESS [1.858s] > [INFO] Log4J Core ........................................ SUCCESS [2.806s] > [INFO] Log4J Compatibility API ........................... SUCCESS [4.260s] > [INFO] SLF4J Binding ..................................... SUCCESS [0.426s] > [INFO] Log4J Commons Logging ............................. SUCCESS [0.595s] > [INFO] Log4J Flume NG .................................... FAILURE [20.160s] > [INFO] Log4j Web Adapters ................................ SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 32.304s > [INFO] Finished at: Wed Sep 26 17:13:59 EDT 2012 > [INFO] Final Memory: 26M/208M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.felix:maven-bundle-plugin:2.3.7:manifest (bundle-manifest) on > project log4j-flume-ng: Error(s) found in manifest confi > guration -> [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-flume-ng > > Almost there! > > Gary > > On Wed, Sep 26, 2012 at 1:33 PM, Gary Gregory <[email protected]> wrote: > I am not sure the snapshot is there yet. With "mvn clean eclipse:eclipse": > > [INFO] > > [INFO] > ------------------------------------------------------------------------ > [INFO] Building Log4J Compatibility API 2.0-beta2-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ log4j12-api --- > [INFO] Deleting C:\svn\org\apache\log4j2\trunk\log4j12-api\target > [INFO] > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j12-api >>> > [INFO] > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j12-api > --- > > [INFO] > ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Apache Log4j 2 .................................... SUCCESS [1.203s] > [INFO] Log4J API ......................................... SUCCESS [0.256s] > [INFO] Log4J Core ........................................ SUCCESS [0.628s] > [INFO] Log4J Compatibility API ........................... FAILURE [0.361s] > > [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: 5.675s > [INFO] Finished at: Wed Sep 26 13:30:36 EDT 2012 > [INFO] Final Memory: 19M/214M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default) > on project log4j12-api: Failed to resolve dependenci > es for one or more projects in the reactor. Reason: Missing: > [ERROR] ---------- > [ERROR] 1) > org.apache.logging.log4j:log4j-core:test-jar:tests: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-core -Dversion=2.0-beta2-SNAPSHOT -Dclassifier=tests > -Dpackaging=test-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-core -Dversion=2.0-beta2-SNAPSHOT -Dclassifier=tests > -Dpackaging=test-jar - > Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > [ERROR] > [ERROR] Path to dependency: > [ERROR] 1) > org.apache.logging.log4j.adapters:log4j12-api:jar:2.0-beta2-SNAPSHOT > [ERROR] 2) > org.apache.logging.log4j:log4j-core:test-jar:tests:2.0-beta2-SNAPSHOT > > [ERROR] > [ERROR] ---------- > [ERROR] 1 required artifact is missing. > [ERROR] > [ERROR] for artifact: > [ERROR] org.apache.logging.log4j.adapters:log4j12-api: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 :log4j12-api > > > Gary > > > On Wed, Sep 26, 2012 at 12:48 PM, Ralph Goers <[email protected]> > wrote: > I deployed the snapshots. You should be able to run "mvn eclipse:eclipse" now. > Ralph > > On Sep 26, 2012, at 9:33 AM, Ralph Goers wrote: > >> Yeah - I forgot about that. The other projects use the test classes from >> core. But those aren't generated if you skip tests. >> >> The simplest way around this is for me to just deploy a snapshot for you. >> >> Ralph >> >> >> On Sep 26, 2012, at 8:36 AM, Gary Gregory wrote: >> >>> I got the latest from SVN and I run the command you gave but I get: >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Log4J Compatibility API 2.0-beta2-SNAPSHOT >>> [INFO] >>> ------------------------------------------------------------------------ >>> Downloading: >>> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-core/2.0-beta2-SNAPSHOT/log4j-core-2.0-beta2-SNAPSHOT-tests.jar >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Reactor Summary: >>> [INFO] >>> [INFO] Apache Log4j 2 .................................... SUCCESS [5.809s] >>> [INFO] Log4J API ......................................... SUCCESS [5.443s] >>> [INFO] Log4J Core ........................................ SUCCESS [7.759s] >>> [INFO] Log4J Compatibility API ........................... FAILURE [1.670s] >>> [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: 22.066s >>> [INFO] Finished at: Wed Sep 26 11:35:24 EDT 2012 >>> [INFO] Final Memory: 23M/120M >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] Failed to execute goal on project log4j12-api: Could not resolve >>> dependencies for project >>> org.apache.logging.log4j.adapters:log4j12-api:jar:2.0-beta2-SN >>> APSHOT: Could not find artifact >>> org.apache.logging.log4j:log4j-core:jar:tests:2.0-beta2-SNAPSHOT in >>> apache.snapshots (http://repository.apache.org/snapshots) -> >>> [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 :log4j12-api >>> >>> Gary >>> >>> On Wed, Sep 26, 2012 at 11:26 AM, Ralph Goers <[email protected]> >>> wrote: >>> I've fixed PatternParserTest but I still have to fix the other one. It has >>> something to do with File.setLastModified. In the meantime, to run mvn >>> eclipse:eclipse first do "mvn clean install -Dmaven.test.skip" >>> >>> Ralph >>> >>> >>> >>> On Sep 26, 2012, at 6:31 AM, Ralph Goers wrote: >>> >>>> I ran the build in my Windows VM and I see those 2 failures. I will take a >>>> look. >>>> >>>> Ralph >>>> >>>> On Sep 26, 2012, at 6:03 AM, Ralph Goers wrote: >>>> >>>>> 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 >>>>> >>>> >>> >>> >>> >>> >>> -- >>> 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 >> > > > > > -- > 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 > > > > -- > 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
