I don't use Eclipse (can't stand the thing), so I hesitate to hazard a guess.
My gut feeling is it sounds like a bug in the Maven Eclipse Plugin. The error
message and URL definitely indicates that the error originated in the plugin. I
would try running with -e to see the full error stack trace. If that doesn't
help, try -X to get full debug mode. It rather sucks that it says "Cant
canonicalize system path: {0}" but doesn't tell you what that path is. That
path information sure would help determine what the problem was. Maybe debug or
stack trace mode will help indicate what the path is that it can't canonicalize.
You could also always try a real IDE. http://www.jetbrains.com/idea/ ;-) (By
the way, Ultimate Edition is free for us FOSS folks.)
Nick
On May 16, 2013, at 4:49 PM, Gary Gregory wrote:
> Nice work Nick.
>
> The last wrinkle for Eclipse users is that running, which is not new, is
> running "mvn eclipse:eclipse" works until the last sample:
>
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.101s]
> [INFO] Apache Log4j API .................................. SUCCESS [0.256s]
> [INFO] Apache Log4j Core ................................. SUCCESS [1.604s]
> [INFO] Apache Log4j 1.x Compatibility API ................ SUCCESS [0.216s]
> [INFO] Apache Log4j SLF4J Binding ........................ SUCCESS [0.222s]
> [INFO] Apache Log4j to SLF4J Adapter ..................... SUCCESS [0.163s]
> [INFO] Apache Log4j Commons Logging Bridge ............... SUCCESS [0.136s]
> [INFO] Apache Log4j Flume NG Bridge ...................... SUCCESS [1.174s]
> [INFO] Apache Log4j Web Adapters ......................... SUCCESS [0.135s]
> [INFO] Apache Log4j Tag Library .......................... SUCCESS [0.156s]
> [INFO] Apache Log4j JMX GUI .............................. SUCCESS [0.107s]
> [INFO] Apache Log4j Samples .............................. SUCCESS [0.082s]
> [INFO] Apache Log4j Samples: Flume - Common .............. SUCCESS [0.508s]
> [INFO] Apache Log4j Samples: Flume - Remote .............. FAILURE [0.769s]
> [INFO] Apache Log4j Samples: Flume - Embedded ............ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 8.584s
> [INFO] Finished at: Thu May 16 17:47:35 EDT 2013
> [INFO] Final Memory: 38M/598M
> [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}: The
> filename, directory name, or volume label syntax
> is incorrect -> [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
>
> Thoughts on that?
>
> Gary
>
>
> On Thu, May 16, 2013 at 5:23 PM, Nick Williams
> <[email protected]> wrote:
> - There were >400 use cases of "Log4j" in documentation, but around 100 use
> cases of "Log4J." All uses of "Log4J" have been changed to "Log4j."
>
> - There were dozens of classes with "Log4j" in their names, but a handful had
> "Log4J" in their name. All uses of "Log4J" have been changed to "Log4j."
>
> - There were >100 use cases of "Log4j 2" in documentation, but a dozen or so
> "Log4j2." All uses of "Log4j2" have been changed to "Log4j 2."
>
> - The sample artifacts all start with "log4j-samples" now.
>
> - The sample artifacts have real names now instead of falling back to their
> artifact IDs.
>
> - In the process of doing this, I incidentally correct many spelling errors
> in documentation. At some point I need to run spell check on the entire
> project...
>
> This is all committed. Everything compiles, all tests pass, site looks great.
>
> Nick
>
> On May 16, 2013, at 1:00 PM, Gary Gregory wrote:
>
>> On Thu, May 16, 2013 at 1:43 PM, Nick Williams
>> <[email protected]> wrote:
>> If I understand correctly, you want the last four (all samples) to be:
>>
>> log4j-samples
>> log4j-samples-common
>> log4j-samples-remote
>> log4j-samples-embedded
>>
>> And you also want them to have names as apposed to just IDs. I'll make some
>> further observations:
>>
>> - Core and JMX GUI should start with "Apache Log4j" (lowercase J) like the
>> other artifacts, not "Apache Log4J" (uppercase J).
>> - It seems to me like ALL of the artifacts should start with "Apache Log4j
>> 2" to eliminate any ambiguity.
>> - Throughout the site and documentation "Log4j" and "Log4J" are intermixed.
>> I think we should stick to "Log4j" and make it consistent everywhere. I can
>> easily do a case-sensitive search and clean this up.
>>
>> I can take care of all of these if you'd like.
>>
>> That would be great!
>>
>> Thank you,
>> Gary
>>
>>
>> Nick
>>
>> On May 16, 2013, at 12:31 PM, Gary Gregory wrote:
>>
>>> Right now we have, as seen in M3 output:
>>>
>>> [INFO] Apache Log4j 2
>>> [INFO] Apache Log4j API
>>> [INFO] Apache Log4J Core
>>> [INFO] Apache Log4j 1.x Compatibility API
>>> [INFO] Apache Log4j SLF4J Binding
>>> [INFO] Apache Log4j to SLF4J Adapter
>>> [INFO] Apache Log4j Commons Logging Bridge
>>> [INFO] Apache Log4j Flume NG Bridge
>>> [INFO] Apache Log4j Web Adapters
>>> [INFO] Apache Log4j Tag Library
>>> [INFO] Apache Log4J JMX GUI
>>> [INFO] log4j-samples
>>> [INFO] flume-common
>>> [INFO] flume-remote
>>> [INFO] flume-embedded
>>>
>>> The last four should be renamed, which means changing the artifact IDs, to
>>> match the log4j prefix.
>>>
>>> I ran into some odd problems when I tried to do that and gave up.
>>>
>>> Gary
>>>
>>> --
>>> E-Mail: [email protected] | [email protected]
>>> Java Persistence with Hibernate, Second Edition
>>> JUnit in Action, Second Edition
>>> Spring Batch in Action
>>> Blog: http://garygregory.wordpress.com
>>> Home: http://garygregory.com/
>>> Tweet! http://twitter.com/GaryGregory
>>
>>
>>
>>
>> --
>> E-Mail: [email protected] | [email protected]
>> Java Persistence with Hibernate, Second Edition
>> JUnit in Action, Second Edition
>> Spring Batch in Action
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>
>
>
>
> --
> E-Mail: [email protected] | [email protected]
> Java Persistence with Hibernate, Second Edition
> JUnit in Action, Second Edition
> Spring Batch in Action
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
