logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Remko Popma <remko.po...@gmail.com>
Subject Re: Log4j2 setup in Eclipse
Date Thu, 15 Aug 2013 04:36:46 GMT
Update:
"Typically, the cause of this is because a POM author put a replaceable
like $
{basedir} in the target or directory tags. This is not allowed. Target and
Directory tags are relative to the POM, and are not supposed to have drive
letters and paths to roots of the filesystem."
http://jira.codehaus.org/browse/MECLIPSE-269

I'll tinker some more...


On Thu, Aug 15, 2013 at 1:30 PM, Remko Popma <remko.popma@gmail.com> wrote:

> Gary, thanks. I'm getting the same error you had some time ago. Were you
> able to fix that?
>
> [INFO] Using Eclipse Workspace: C:\Users\remko\workspace
> [INFO] Adding default classpath container:
> org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.143s]
> [INFO] Apache Log4j API .................................. SUCCESS [0.230s]
> [INFO] Apache Log4j Core ................................. SUCCESS [0.884s]
> [INFO] Apache Log4J Core OSGi Async ...................... SUCCESS [1.076s]
> [INFO] Apache Log4J Core OSGi JPA ........................ SUCCESS [0.213s]
> [INFO] Apache Log4J Core OSGi Net ........................ SUCCESS [0.216s]
> [INFO] Apache Log4J Core OSGi Couch ...................... SUCCESS [0.163s]
> [INFO] Apache Log4J Core OSGi Mongo ...................... SUCCESS [0.171s]
> [INFO] Apache Log4J Core OSGi ............................ SUCCESS [0.151s]
> [INFO] Apache Log4J Core OSGi Bundles .................... SUCCESS [0.043s]
> [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [0.164s]
> [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [0.165s]
> [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [0.437s]
> [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [0.111s]
> [INFO] Apache Log4j Flume NG Bridge ...................... SUCCESS [1.189s]
> [INFO] Apache Log4j Tag Library .......................... SUCCESS [0.132s]
> [INFO] Apache Log4j JMX GUI .............................. SUCCESS [0.107s]
> [INFO] Apache Log4j Samples .............................. SUCCESS [0.065s]
> [INFO] Apache Log4j Samples: Flume - Common .............. SUCCESS [0.420s]
> [INFO] Apache Log4j Samples: Flume - Remote .............. FAILURE [0.641s]
> [INFO] Apache Log4j Samples: Flume - Embedded ............ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 10.068s
> [INFO] Finished at: Thu Aug 15 12:57:10 JST 2013
> [INFO] Final Memory: 36M/315M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-eclipse-plugin:2.9:eclipse (default-cli) on
> project log4j-
> samples-flume-remote: Cant canonicalize system path: {0}:
> ファイル名、ディレクトリ名、またはボリューム ラベルの構文が間
> 違っています。 -> [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-samples-flume-remote
> C:\Users\remko\workspace\log4j2>
>
>
>
> On Thu, Aug 15, 2013 at 12:27 PM, Gary Gregory <garydgregory@gmail.com>wrote:
>
>> Use "mvn eclipse:eclipse" in the root and it will generate all the
>> eclipse files you need. Then you can just import the projects in eclipse.
>> M2E has never worked for me.
>>
>> Gary
>>
>> On Aug 14, 2013, at 21:58, Paul Benedict <pbenedict@apache.org> wrote:
>>
>> Are you using the m2e plugin for Eclipse? If not, install it from Eclipse
>> Marketplace. You'll also need its subclipse or subversive plugin so you can
>> check out as a Maven project and it will be there.
>>
>> Paul
>>
>>
>> On Wed, Aug 14, 2013 at 8:30 PM, Remko Popma <remko.popma@gmail.com>wrote:
>>
>>> I don't mean to start a discussion on which IDE is best (please).
>>>
>>> Does anyone have a way to set up the log4j2 project in Eclipse so that
>>> all modules compile? And can you send me the Eclipse config files to
>>> accomplish that?
>>>
>>> I currently manually update the classpath by pointing to jars in my
>>> local .m2/repository but it's a pain to keep this up to date. Surely there
>>> is a better way?
>>>
>>> Also, is anyone able to run all JUnit test in their IDE?
>>> Some JUnit tests I can run locally in my IDE (which means I can run them
>>> in the debugger) but many others only pass when run in Maven (which means I
>>> *cannot* run them in the debugger...)
>>>
>>> Remko
>>>
>>
>>
>>
>> --
>> Cheers,
>> Paul
>>
>>
>

Mime
View raw message