You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Rainer Hirschmiller <ra...@web.de> on 2012/08/20 18:03:03 UTC
log4j2: building trunk
Hi,
trying to build the trunk I got an error. Here is my message printed
during build:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for
org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-
pmd-plugin is missing. @ line 242, column 15
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten t
he stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
buildin
g such malformed projects.
[WARNING]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Log4j 2
[INFO] Log4J API
[INFO] Log4J Core
[INFO] Log4J Compatibility API
[INFO] SLF4J Binding
[INFO] Log4J Commons Logging
[INFO] Log4J Flume NG
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus
.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO]
[INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
[INFO] Not running eclipse plugin goal for pom project
[INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar: D
:\jdk1.7.0\jre
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAIN
ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @
log4j-api ---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
[INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
[WARNING] Workspace defines a VM that does not contain a valid
jre/lib/rt.jar: D
:\jdk1.7.0\jre
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAIN
ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
[INFO] Wrote settings to
Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
ore.prefs
[INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
[INFO]
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
[INFO] Log4J API ......................................... SUCCESS [0.469s]
[INFO] Log4J Core ........................................ FAILURE [0.375s]
[INFO] Log4J Compatibility API ........................... SKIPPED
[INFO] SLF4J Binding ..................................... SKIPPED
[INFO] Log4J Commons Logging ............................. SKIPPED
[INFO] Log4J Flume NG .................................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 6.985s
[INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
[INFO] Final Memory: 14M/36M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-p
lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy
the file t
here:
[ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j
-DartifactId=l
og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Dur
l=[url] -DrepositoryId=[id]
[ERROR]
[ERROR] Path to dependency:
[ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
[ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
[ERROR]
[ERROR] ----------
[ERROR] 1 required artifact is missing.
[ERROR]
[ERROR] for artifact:
[ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
alse)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :log4j-core
Z:\Projekte.JUNO\log4j2>
How can I fix the problem?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
AW: log4j2: building trunk
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Rainer,
could you make
$ mvn install
run meanwhile?
I suggest to try the "mvn install" without Eclips first.
Run "mvn install" from a DOS window, or a Eclips Termina Window, if Eclips provides one.
The next thing to consider is the environment in which you intend to run "mvn install".
you can do "$ mcn help:system" to see the environment as maven sees it.
In which environment, in which Java VM environment is Eclips running?
Is maven using the same environment?
May you can you launch a Terminal by Eclips and then do a
$ set
to see what environment variables are defined for DOS in that context.
in the same Terminal you can the run
$ pwd
$ cd /<your prject dir>
$ mvn help:system
$ mvn help:effective-settings
$ mvn help:effective-pom
How do you setup the workspace in Eclips? I aske this because in your logs you can find
[WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D :\jdk1.7.0\jre
Maybe you can check the Eclips environment and find out why this warning happens.
Maybe there is just a space too much, and it should read D:\jdk1.7.0\jre not "D :"
And then yes, try to skip the tests as Ralph points out.
Best do a
$ mvn install -Dmaven.test.skip
from your 1. DOS and 2. Eclips Terminal Window 3. then with Eclips
Running successfully from DOS windows will definitely lead you the way to your problem.
Josef
-----Ursprüngliche Nachricht-----
Von: Ralph Goers [mailto:ralph.goers@dslextreme.com]
Gesendet: Montag, 20. August 2012 19:02
An: Log4J Users List
Betreff: Re: log4j2: building trunk
I should add, though, that I have a suspicion that the error is due to our locale differences.
Ralph
On Aug 20, 2012, at 10:00 AM, Ralph Goers wrote:
> First, would you please look in log4j12-api\target\surefire-reports for org.apache.log4j.LoggerTest.txt and attach that so I can see why the test failed?
>
> Second, you can run "mvn install -Dmaven.test.skip" to skip the unit tests. That should allow you to then run mvn eclipse:eclipse.
>
> Although I have compiled with Java 7 in OSX and I've compiled with Java 6 in my Windows VM, I must admit I haven't yet tried Java 7 in my Windows VM.
>
> Ralph
>
>
>
> On Aug 20, 2012, at 9:39 AM, Rainer Hirschmiller wrote:
>
>> The logging was the result of the second try. First try shows other messages, similar to following ones.
>>
>> Following messages are produces running "mvn install" in the log4j2 directory. It seems that there are some test failures: (I've run it a second try with -X as suggested)
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Log4j 2 .................................... SUCCESS [12.016s]
>> [INFO] Log4J API ......................................... SUCCESS [19.188s]
>> [INFO] Log4J Core ........................................ SUCCESS [2:24.919s]
>> [INFO] Log4J Compatibility API ........................... FAILURE [5.843s]
>> [INFO] SLF4J Binding ..................................... SKIPPED
>> [INFO] Log4J Commons Logging ............................. SKIPPED
>> [INFO] Log4J Flume NG .................................... SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 3:02.686s
>> [INFO] Finished at: Mon Aug 20 18:27:48 CEST 2012
>> [INFO] Final Memory: 21M/64M
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
>> 7.2:test (default-test) on project log4j12-api: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to Z:\Projekte.JUNO\log4j2\log4j12-api\target\surefire-repo
>> rts for the individual test results.
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>> ch.
>> [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 rea
>> d the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>> eption
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the command
>>
>>
>> second try with -X
>> (see attachment)
>>
>>
>> Rainer
>>
>>
>>
>>
>> [ERROR] mvn <goals> -rf :log4j12-api
>>
>>
>>
>> Am 20.08.2012 18:09, schrieb Ralph Goers:
>>> Are you running "mvn eclipse:eclipse"? If so, run "mvn install" first. That will install the artifacts into your local repository so that the eclipse goal can find them.
>>>
>>> Ralph
>>>
>>> On Aug 20, 2012, at 9:03 AM, Rainer Hirschmiller wrote:
>>>
>>>> Hi,
>>>>
>>>> trying to build the trunk I got an error. Here is my message printed during build:
>>>>
>>>> [INFO] Scanning for projects...
>>>> [WARNING]
>>>> [WARNING] Some problems were encountered while building the effective model for
>>>> org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
>>>> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-
>>>> pmd-plugin is missing. @ line 242, column 15
>>>> [WARNING]
>>>> [WARNING] It is highly recommended to fix these problems because they threaten t
>>>> he stability of your build.
>>>> [WARNING]
>>>> [WARNING] For this reason, future Maven versions might no longer support buildin
>>>> g such malformed projects.
>>>> [WARNING]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Reactor Build Order:
>>>> [INFO]
>>>> [INFO] Apache Log4j 2
>>>> [INFO] Log4J API
>>>> [INFO] Log4J Core
>>>> [INFO] Log4J Compatibility API
>>>> [INFO] SLF4J Binding
>>>> [INFO] Log4J Commons Logging
>>>> [INFO] Log4J Flume NG
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
>>>> [INFO]
>>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
>>>> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus
>>>> .velocity.ContextClassLoaderResourceLoader'.
>>>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>>>> [INFO] Setting property: resource.loader => 'classpath'.
>>>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>>>> [INFO]
>>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
>>>> [INFO]
>>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
>>>> [INFO] Not running eclipse plugin goal for pom project
>>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>>> :\jdk1.7.0\jre
>>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
>>>> [INFO]
>>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
>>>> [INFO]
>>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
>>>> [INFO]
>>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
>>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>>> :\jdk1.7.0\jre
>>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>>> [INFO] Wrote settings to Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
>>>> ore.prefs
>>>> [INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
>>>> [INFO]
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
>>>> [INFO] Log4J API ......................................... SUCCESS [0.469s]
>>>> [INFO] Log4J Core ........................................ FAILURE [0.375s]
>>>> [INFO] Log4J Compatibility API ........................... SKIPPED
>>>> [INFO] SLF4J Binding ..................................... SKIPPED
>>>> [INFO] Log4J Commons Logging ............................. SKIPPED
>>>> [INFO] Log4J Flume NG .................................... SKIPPED
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: 6.985s
>>>> [INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
>>>> [INFO] Final Memory: 14M/36M
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-p
>>>> lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>>>> [ERROR]
>>>> [ERROR] Alternatively, if you host your own repository you can deploy the file t
>>>> here:
>>>> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j -DartifactId=l
>>>> og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Dur
>>>> l=[url] -DrepositoryId=[id]
>>>> [ERROR]
>>>> [ERROR] Path to dependency:
>>>> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
>>>> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
>>>> [ERROR]
>>>> [ERROR] ----------
>>>> [ERROR] 1 required artifact is missing.
>>>> [ERROR]
>>>> [ERROR] for artifact:
>>>> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
>>>> alse)
>>>> [ERROR] -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>>>> ch.
>>>> [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 rea
>>>> d the following articles:
>>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
>>>> xception
>>>> [ERROR]
>>>> [ERROR] After correcting the problems, you can resume the build with the command
>>>>
>>>> [ERROR] mvn <goals> -rf :log4j-core
>>>> Z:\Projekte.JUNO\log4j2>
>>>>
>>>> How can I fix the problem?
>>>>
>>>>
>>>> Rainer
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>
>> <logging.txt>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j2: building trunk
Posted by Ralph Goers <ra...@dslextreme.com>.
I should add, though, that I have a suspicion that the error is due to our locale differences.
Ralph
On Aug 20, 2012, at 10:00 AM, Ralph Goers wrote:
> First, would you please look in log4j12-api\target\surefire-reports for org.apache.log4j.LoggerTest.txt and attach that so I can see why the test failed?
>
> Second, you can run "mvn install -Dmaven.test.skip" to skip the unit tests. That should allow you to then run mvn eclipse:eclipse.
>
> Although I have compiled with Java 7 in OSX and I've compiled with Java 6 in my Windows VM, I must admit I haven't yet tried Java 7 in my Windows VM.
>
> Ralph
>
>
>
> On Aug 20, 2012, at 9:39 AM, Rainer Hirschmiller wrote:
>
>> The logging was the result of the second try. First try shows other messages, similar to following ones.
>>
>> Following messages are produces running "mvn install" in the log4j2 directory. It seems that there are some test failures: (I've run it a second try with -X as suggested)
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Log4j 2 .................................... SUCCESS [12.016s]
>> [INFO] Log4J API ......................................... SUCCESS [19.188s]
>> [INFO] Log4J Core ........................................ SUCCESS [2:24.919s]
>> [INFO] Log4J Compatibility API ........................... FAILURE [5.843s]
>> [INFO] SLF4J Binding ..................................... SKIPPED
>> [INFO] Log4J Commons Logging ............................. SKIPPED
>> [INFO] Log4J Flume NG .................................... SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 3:02.686s
>> [INFO] Finished at: Mon Aug 20 18:27:48 CEST 2012
>> [INFO] Final Memory: 21M/64M
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
>> 7.2:test (default-test) on project log4j12-api: There are test failures.
>> [ERROR]
>> [ERROR] Please refer to Z:\Projekte.JUNO\log4j2\log4j12-api\target\surefire-repo
>> rts for the individual test results.
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>> ch.
>> [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 rea
>> d the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>> eption
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the command
>>
>>
>> second try with -X
>> (see attachment)
>>
>>
>> Rainer
>>
>>
>>
>>
>> [ERROR] mvn <goals> -rf :log4j12-api
>>
>>
>>
>> Am 20.08.2012 18:09, schrieb Ralph Goers:
>>> Are you running "mvn eclipse:eclipse"? If so, run "mvn install" first. That will install the artifacts into your local repository so that the eclipse goal can find them.
>>>
>>> Ralph
>>>
>>> On Aug 20, 2012, at 9:03 AM, Rainer Hirschmiller wrote:
>>>
>>>> Hi,
>>>>
>>>> trying to build the trunk I got an error. Here is my message printed during build:
>>>>
>>>> [INFO] Scanning for projects...
>>>> [WARNING]
>>>> [WARNING] Some problems were encountered while building the effective model for
>>>> org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
>>>> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-
>>>> pmd-plugin is missing. @ line 242, column 15
>>>> [WARNING]
>>>> [WARNING] It is highly recommended to fix these problems because they threaten t
>>>> he stability of your build.
>>>> [WARNING]
>>>> [WARNING] For this reason, future Maven versions might no longer support buildin
>>>> g such malformed projects.
>>>> [WARNING]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Reactor Build Order:
>>>> [INFO]
>>>> [INFO] Apache Log4j 2
>>>> [INFO] Log4J API
>>>> [INFO] Log4J Core
>>>> [INFO] Log4J Compatibility API
>>>> [INFO] SLF4J Binding
>>>> [INFO] Log4J Commons Logging
>>>> [INFO] Log4J Flume NG
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
>>>> [INFO]
>>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
>>>> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus
>>>> .velocity.ContextClassLoaderResourceLoader'.
>>>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>>>> [INFO] Setting property: resource.loader => 'classpath'.
>>>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>>>> [INFO]
>>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
>>>> [INFO]
>>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
>>>> [INFO] Not running eclipse plugin goal for pom project
>>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>>> :\jdk1.7.0\jre
>>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
>>>> [INFO]
>>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
>>>> [INFO]
>>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
>>>> [INFO]
>>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
>>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>>> :\jdk1.7.0\jre
>>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>>> [INFO] Wrote settings to Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
>>>> ore.prefs
>>>> [INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
>>>> [INFO]
>>>> [INFO]
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO]
>>>> [INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
>>>> [INFO] Log4J API ......................................... SUCCESS [0.469s]
>>>> [INFO] Log4J Core ........................................ FAILURE [0.375s]
>>>> [INFO] Log4J Compatibility API ........................... SKIPPED
>>>> [INFO] SLF4J Binding ..................................... SKIPPED
>>>> [INFO] Log4J Commons Logging ............................. SKIPPED
>>>> [INFO] Log4J Flume NG .................................... SKIPPED
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Total time: 6.985s
>>>> [INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
>>>> [INFO] Final Memory: 14M/36M
>>>> [INFO] ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-p
>>>> lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>>>> [ERROR]
>>>> [ERROR] Alternatively, if you host your own repository you can deploy the file t
>>>> here:
>>>> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j -DartifactId=l
>>>> og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Dur
>>>> l=[url] -DrepositoryId=[id]
>>>> [ERROR]
>>>> [ERROR] Path to dependency:
>>>> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
>>>> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
>>>> [ERROR]
>>>> [ERROR] ----------
>>>> [ERROR] 1 required artifact is missing.
>>>> [ERROR]
>>>> [ERROR] for artifact:
>>>> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
>>>> alse)
>>>> [ERROR] -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>>>> ch.
>>>> [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 rea
>>>> d the following articles:
>>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
>>>> xception
>>>> [ERROR]
>>>> [ERROR] After correcting the problems, you can resume the build with the command
>>>>
>>>> [ERROR] mvn <goals> -rf :log4j-core
>>>> Z:\Projekte.JUNO\log4j2>
>>>>
>>>> How can I fix the problem?
>>>>
>>>>
>>>> Rainer
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>>
>>
>> <logging.txt>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j2: building trunk
Posted by Ralph Goers <ra...@dslextreme.com>.
First, would you please look in log4j12-api\target\surefire-reports for org.apache.log4j.LoggerTest.txt and attach that so I can see why the test failed?
Second, you can run "mvn install -Dmaven.test.skip" to skip the unit tests. That should allow you to then run mvn eclipse:eclipse.
Although I have compiled with Java 7 in OSX and I've compiled with Java 6 in my Windows VM, I must admit I haven't yet tried Java 7 in my Windows VM.
Ralph
On Aug 20, 2012, at 9:39 AM, Rainer Hirschmiller wrote:
> The logging was the result of the second try. First try shows other messages, similar to following ones.
>
> Following messages are produces running "mvn install" in the log4j2 directory. It seems that there are some test failures: (I've run it a second try with -X as suggested)
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [12.016s]
> [INFO] Log4J API ......................................... SUCCESS [19.188s]
> [INFO] Log4J Core ........................................ SUCCESS [2:24.919s]
> [INFO] Log4J Compatibility API ........................... FAILURE [5.843s]
> [INFO] SLF4J Binding ..................................... SKIPPED
> [INFO] Log4J Commons Logging ............................. SKIPPED
> [INFO] Log4J Flume NG .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 3:02.686s
> [INFO] Finished at: Mon Aug 20 18:27:48 CEST 2012
> [INFO] Final Memory: 21M/64M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.
> 7.2:test (default-test) on project log4j12-api: There are test failures.
> [ERROR]
> [ERROR] Please refer to Z:\Projekte.JUNO\log4j2\log4j12-api\target\surefire-repo
> rts for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
> ch.
> [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 rea
> d the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
> eption
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
>
>
> second try with -X
> (see attachment)
>
>
> Rainer
>
>
>
>
> [ERROR] mvn <goals> -rf :log4j12-api
>
>
>
> Am 20.08.2012 18:09, schrieb Ralph Goers:
>> Are you running "mvn eclipse:eclipse"? If so, run "mvn install" first. That will install the artifacts into your local repository so that the eclipse goal can find them.
>>
>> Ralph
>>
>> On Aug 20, 2012, at 9:03 AM, Rainer Hirschmiller wrote:
>>
>>> Hi,
>>>
>>> trying to build the trunk I got an error. Here is my message printed during build:
>>>
>>> [INFO] Scanning for projects...
>>> [WARNING]
>>> [WARNING] Some problems were encountered while building the effective model for
>>> org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
>>> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-
>>> pmd-plugin is missing. @ line 242, column 15
>>> [WARNING]
>>> [WARNING] It is highly recommended to fix these problems because they threaten t
>>> he stability of your build.
>>> [WARNING]
>>> [WARNING] For this reason, future Maven versions might no longer support buildin
>>> g such malformed projects.
>>> [WARNING]
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Reactor Build Order:
>>> [INFO]
>>> [INFO] Apache Log4j 2
>>> [INFO] Log4J API
>>> [INFO] Log4J Core
>>> [INFO] Log4J Compatibility API
>>> [INFO] SLF4J Binding
>>> [INFO] Log4J Commons Logging
>>> [INFO] Log4J Flume NG
>>> [INFO]
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO]
>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
>>> [INFO]
>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
>>> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus
>>> .velocity.ContextClassLoaderResourceLoader'.
>>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>>> [INFO] Setting property: resource.loader => 'classpath'.
>>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>>> [INFO]
>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
>>> [INFO]
>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
>>> [INFO] Not running eclipse plugin goal for pom project
>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>> :\jdk1.7.0\jre
>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>> [INFO]
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO]
>>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
>>> [INFO]
>>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
>>> [INFO]
>>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
>>> [INFO]
>>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
>>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>>> :\jdk1.7.0\jre
>>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>>> [INFO] Wrote settings to Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
>>> ore.prefs
>>> [INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
>>> [INFO]
>>> [INFO]
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO]
>>> [INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
>>> [INFO] Log4J API ......................................... SUCCESS [0.469s]
>>> [INFO] Log4J Core ........................................ FAILURE [0.375s]
>>> [INFO] Log4J Compatibility API ........................... SKIPPED
>>> [INFO] SLF4J Binding ..................................... SKIPPED
>>> [INFO] Log4J Commons Logging ............................. SKIPPED
>>> [INFO] Log4J Flume NG .................................... SKIPPED
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Total time: 6.985s
>>> [INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
>>> [INFO] Final Memory: 14M/36M
>>> [INFO] ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-p
>>> lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>>> [ERROR]
>>> [ERROR] Alternatively, if you host your own repository you can deploy the file t
>>> here:
>>> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j -DartifactId=l
>>> og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Dur
>>> l=[url] -DrepositoryId=[id]
>>> [ERROR]
>>> [ERROR] Path to dependency:
>>> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
>>> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
>>> [ERROR]
>>> [ERROR] ----------
>>> [ERROR] 1 required artifact is missing.
>>> [ERROR]
>>> [ERROR] for artifact:
>>> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
>>> alse)
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>>> ch.
>>> [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 rea
>>> d the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
>>> xception
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the command
>>>
>>> [ERROR] mvn <goals> -rf :log4j-core
>>> Z:\Projekte.JUNO\log4j2>
>>>
>>> How can I fix the problem?
>>>
>>>
>>> Rainer
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
>
> <logging.txt>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: log4j2: building trunk
Posted by Rainer Hirschmiller <ra...@web.de>.
The logging was the result of the second try. First try shows other
messages, similar to following ones.
Following messages are produces running "mvn install" in the log4j2
directory. It seems that there are some test failures: (I've run it a
second try with -X as suggested)
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [12.016s]
[INFO] Log4J API ......................................... SUCCESS [19.188s]
[INFO] Log4J Core ........................................ SUCCESS
[2:24.919s]
[INFO] Log4J Compatibility API ........................... FAILURE [5.843s]
[INFO] SLF4J Binding ..................................... SKIPPED
[INFO] Log4J Commons Logging ............................. SKIPPED
[INFO] Log4J Flume NG .................................... SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3:02.686s
[INFO] Finished at: Mon Aug 20 18:27:48 CEST 2012
[INFO] Final Memory: 21M/64M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.
7.2:test (default-test) on project log4j12-api: There are test failures.
[ERROR]
[ERROR] Please refer to
Z:\Projekte.JUNO\log4j2\log4j12-api\target\surefire-repo
rts for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e swit
ch.
[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 rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
eption
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
second try with -X
(see attachment)
Rainer
[ERROR] mvn <goals> -rf :log4j12-api
Am 20.08.2012 18:09, schrieb Ralph Goers:
> Are you running "mvn eclipse:eclipse"? If so, run "mvn install" first. That will install the artifacts into your local repository so that the eclipse goal can find them.
>
> Ralph
>
> On Aug 20, 2012, at 9:03 AM, Rainer Hirschmiller wrote:
>
>> Hi,
>>
>> trying to build the trunk I got an error. Here is my message printed during build:
>>
>> [INFO] Scanning for projects...
>> [WARNING]
>> [WARNING] Some problems were encountered while building the effective model for
>> org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
>> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-
>> pmd-plugin is missing. @ line 242, column 15
>> [WARNING]
>> [WARNING] It is highly recommended to fix these problems because they threaten t
>> he stability of your build.
>> [WARNING]
>> [WARNING] For this reason, future Maven versions might no longer support buildin
>> g such malformed projects.
>> [WARNING]
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Build Order:
>> [INFO]
>> [INFO] Apache Log4j 2
>> [INFO] Log4J API
>> [INFO] Log4J Core
>> [INFO] Log4J Compatibility API
>> [INFO] SLF4J Binding
>> [INFO] Log4J Commons Logging
>> [INFO] Log4J Flume NG
>> [INFO]
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
>> [INFO] ------------------------------------------------------------------------
>> [INFO]
>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
>> [INFO]
>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
>> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus
>> .velocity.ContextClassLoaderResourceLoader'.
>> [INFO] Setting property: velocimacro.messages.on => 'false'.
>> [INFO] Setting property: resource.loader => 'classpath'.
>> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>> [INFO]
>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
>> [INFO]
>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
>> [INFO] Not running eclipse plugin goal for pom project
>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>> :\jdk1.7.0\jre
>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>> [INFO]
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
>> [INFO] ------------------------------------------------------------------------
>> [INFO]
>> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
>> [INFO]
>> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
>> [INFO]
>> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
>> [INFO]
>> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
>> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
>> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
>> :\jdk1.7.0\jre
>> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
>> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
>> [INFO] Wrote settings to Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
>> ore.prefs
>> [INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
>> [INFO]
>> [INFO]
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
>> [INFO] ------------------------------------------------------------------------
>> [INFO]
>> [INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
>> [INFO] Log4J API ......................................... SUCCESS [0.469s]
>> [INFO] Log4J Core ........................................ FAILURE [0.375s]
>> [INFO] Log4J Compatibility API ........................... SKIPPED
>> [INFO] SLF4J Binding ..................................... SKIPPED
>> [INFO] Log4J Commons Logging ............................. SKIPPED
>> [INFO] Log4J Flume NG .................................... SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Total time: 6.985s
>> [INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
>> [INFO] Final Memory: 14M/36M
>> [INFO] ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-p
>> lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
>> [ERROR]
>> [ERROR] Alternatively, if you host your own repository you can deploy the file t
>> here:
>> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j -DartifactId=l
>> og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Dur
>> l=[url] -DrepositoryId=[id]
>> [ERROR]
>> [ERROR] Path to dependency:
>> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
>> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
>> [ERROR]
>> [ERROR] ----------
>> [ERROR] 1 required artifact is missing.
>> [ERROR]
>> [ERROR] for artifact:
>> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
>> alse)
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
>> ch.
>> [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 rea
>> d the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
>> xception
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the command
>>
>> [ERROR] mvn <goals> -rf :log4j-core
>> Z:\Projekte.JUNO\log4j2>
>>
>> How can I fix the problem?
>>
>>
>> Rainer
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
Re: log4j2: building trunk
Posted by Ralph Goers <ra...@dslextreme.com>.
Are you running "mvn eclipse:eclipse"? If so, run "mvn install" first. That will install the artifacts into your local repository so that the eclipse goal can find them.
Ralph
On Aug 20, 2012, at 9:03 AM, Rainer Hirschmiller wrote:
> Hi,
>
> trying to build the trunk I got an error. Here is my message printed during build:
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for
> org.apache.logging.log4j:log4j-flume-ng:jar:2.0-alpha2-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-
> pmd-plugin is missing. @ line 242, column 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten t
> he stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support buildin
> g such malformed projects.
> [WARNING]
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Log4j 2
> [INFO] Log4J API
> [INFO] Log4J Core
> [INFO] Log4J Compatibility API
> [INFO] SLF4J Binding
> [INFO] Log4J Commons Logging
> [INFO] Log4J Flume NG
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache Log4j 2 2.0-alpha2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus
> .velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j ---
> [INFO] Not running eclipse plugin goal for pom project
> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
> :\jdk1.7.0\jre
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Log4J API 2.0-alpha2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.9:eclipse (default-cli) @ log4j-api ---
> [INFO] Using Eclipse Workspace: Z:\Projekte.JUNO
> [WARNING] Workspace defines a VM that does not contain a valid jre/lib/rt.jar: D
> :\jdk1.7.0\jre
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAIN
> ER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5
> [INFO] Wrote settings to Z:\Projekte.JUNO\log4j2\api\.settings\org.eclipse.jdt.c
> ore.prefs
> [INFO] Wrote Eclipse project for "log4j-api" to Z:\Projekte.JUNO\log4j2\api.
> [INFO]
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Log4J Core 2.0-alpha2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.9: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 [3.406s]
> [INFO] Log4J API ......................................... SUCCESS [0.469s]
> [INFO] Log4J Core ........................................ FAILURE [0.375s]
> [INFO] Log4J Compatibility API ........................... SKIPPED
> [INFO] SLF4J Binding ..................................... SKIPPED
> [INFO] Log4J Commons Logging ............................. SKIPPED
> [INFO] Log4J Flume NG .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 6.985s
> [INFO] Finished at: Mon Aug 20 17:59:34 CEST 2012
> [INFO] Final Memory: 14M/36M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-p
> lugin: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-alpha2-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-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the file t
> here:
> [ERROR] mvn deploy:deploy-file -DgroupId=org.apache.logging.log4j -DartifactId=l
> og4j-api -Dversion=2.0-alpha2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Dur
> l=[url] -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-SNAPSHOT
> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha2-SNAPSHOT
> [ERROR]
> [ERROR] ----------
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.apache.logging.log4j:log4j-core:jar:2.0-alpha2-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=f
> alse)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
> ch.
> [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 rea
> d the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionE
> xception
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
>
> [ERROR] mvn <goals> -rf :log4j-core
> Z:\Projekte.JUNO\log4j2>
>
> How can I fix the problem?
>
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org