Did you also clear your local cache and repo? Maybe a corrupted plugin
or configuration file, but it's hard to tell. This exception is also
thrown if you try to access any file named {nul,prn,aux,lpt1,lpt2,con}.*
which is illegal on NT.
Otherwise no idea, but it's probably not a Maven issue.
HTH,
-Lukas
Eric Czarny wrote:
I have no idea why this is happening, Maven just started failing randomly.
The output Maven displays is:
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1
-------------------------------------------------------------------------------
Error reading XML or initializing
The device is not ready
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
Total time : 13 seconds
Finished at : Wednesday, May 14, 2008 8:17:30 PM EDT
Final Memory : 3M/6M
-------------------------------------------------------------------------------
The actual stack trace produced by Maven is:
Exception stack traces :
org.apache.maven.MavenException: Error reading XML or initializing
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:142)
at
org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHousing.java:108)
at
org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManager.java:350)
at
org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManager.java:241)
at
org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:312)
at
org.apache.maven.MavenSession.initializePluginManager(MavenSession.java:206)
at org.apache.maven.MavenSession.initialize(MavenSession.java:173)
at org.apache.maven.cli.App.doMain(App.java:294)
at org.apache.maven.cli.App.main(App.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Caused by: java.io.IOException: The device is not ready
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:395)
at java.io.File.getCanonicalPath(File.java:531)
at org.apache.maven.MavenUtils.makeAbsolutePath(MavenUtils.java:885)
at
org.apache.maven.project.Project.resolveDirectory(Project.java:1069)
at
org.apache.maven.project.Project.resolveDirectories(Project.java:944)
at org.apache.maven.project.Project.initialize(Project.java:596)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:134)
... 14 more
Has anybody ever witnessed this problem? I have tried everything from
grabbing a fresh copy of our code from source control to reinstalling Maven
(and Java). This problem actually happens with any Maven project on my
computer.
- Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]