Re: Debugging Maven error settings [m2]
Assuming you have nothing special in your settings.xml or your hosts file that would redirect things, a simple mvn help:effective-pom should give you an idea as to what repos are being searched. If you do have mirrors etc in settings.xml which complicate things, or you just can't figure it out, then you might want to use a TCP/IP analzer like Ethereal. Wayne On 11/28/07, Chris Helck <[EMAIL PROTECTED]> wrote: > No this doesn't help. Is there anyway to see which repos maven is > checking? > > Thanks, > Chris > > -Original Message- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 28, 2007 10:13 AM > To: Maven Users List > Subject: Re: Debugging Maven error settings [m2] > > On Nov 28, 2007 8:05 AM, Chris Helck <[EMAIL PROTECTED]> wrote: > > I am having trouble understanding the error below. Maven seems unable > > to pull things down from the central repo, and I don't know why. > > > > I can connect to the repo via the web. > > I have deleted by ~/.m2/repository directory. > > The plugin-registry.xml files do not exist. > > I have been playing with the settings.xml files, but I think I've > > undone my changes. I would like to run the goal > > help:effective-settings, but I can't download the maven help plugin. > Catch-22. > > > > Any ideas about what is going on? Or how to debug this type of > > situation? > > You may be running into the default once-per-day check for updates. > If it fails once, Maven won't check [that repository for that plugin] > again until tommorrow. > > Try adding -U to the command line. (Or deleting the plugin directory > from your local repo.) > > -- > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ** > This communication and all information (including, but not limited to, > market prices/levels and data) contained therein (the "Information") is > for informational purposes only, is confidential, may be legally > privileged and is the intellectual property of ICAP plc and its affiliates > ("ICAP") or third parties. No confidentiality or privilege is waived or > lost by any mistransmission. The Information is not, and should not > be construed as, an offer, bid or solicitation in relation to any > financial instrument or as an official confirmation of any transaction. > The Information is not warranted, including, but not limited, as to > completeness, timeliness or accuracy and is subject to change > without notice. ICAP assumes no liability for use or misuse of the > Information. All representations and warranties are expressly > disclaimed. The Information does not necessarily reflect the views of > ICAP. Access to the Information by anyone else other than the > recipient is unauthorized and any disclosure, copying, distribution or > any action taken or omitted to be taken in reliance on it is prohibited. If > you receive this message in error, please immediately delete it and all > copies of it from your system, destroy any hard copies of it and > notify the sender. > ** > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Debugging Maven error settings [m2]
No this doesn't help. Is there anyway to see which repos maven is checking? Thanks, Chris -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 28, 2007 10:13 AM To: Maven Users List Subject: Re: Debugging Maven error settings [m2] On Nov 28, 2007 8:05 AM, Chris Helck <[EMAIL PROTECTED]> wrote: > I am having trouble understanding the error below. Maven seems unable > to pull things down from the central repo, and I don't know why. > > I can connect to the repo via the web. > I have deleted by ~/.m2/repository directory. > The plugin-registry.xml files do not exist. > I have been playing with the settings.xml files, but I think I've > undone my changes. I would like to run the goal > help:effective-settings, but I can't download the maven help plugin. Catch-22. > > Any ideas about what is going on? Or how to debug this type of > situation? You may be running into the default once-per-day check for updates. If it fails once, Maven won't check [that repository for that plugin] again until tommorrow. Try adding -U to the command line. (Or deleting the plugin directory from your local repo.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the "Information") is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates ("ICAP") or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging Maven error settings [m2]
On Nov 28, 2007 8:05 AM, Chris Helck <[EMAIL PROTECTED]> wrote: > I am having trouble understanding the error below. Maven seems unable to > pull things down from the central repo, and I don't know why. > > I can connect to the repo via the web. > I have deleted by ~/.m2/repository directory. > The plugin-registry.xml files do not exist. > I have been playing with the settings.xml files, but I think I've undone > my changes. I would like to run the goal help:effective-settings, but I > can't download the maven help plugin. Catch-22. > > Any ideas about what is going on? Or how to debug this type of > situation? You may be running into the default once-per-day check for updates. If it fails once, Maven won't check [that repository for that plugin] again until tommorrow. Try adding -U to the command line. (Or deleting the plugin directory from your local repo.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Debugging Maven error settings [m2]
I am having trouble understanding the error below. Maven seems unable to pull things down from the central repo, and I don't know why. I can connect to the repo via the web. I have deleted by ~/.m2/repository directory. The plugin-registry.xml files do not exist. I have been playing with the settings.xml files, but I think I've undone my changes. I would like to run the goal help:effective-settings, but I can't download the maven help plugin. Catch-22. Any ideas about what is going on? Or how to debug this type of situation? %< + Error stacktraces are turned on. Maven version: 2.0.7 Java version: 1.6.0_03 OS name: "linux" version: "2.6.22-14-386" arch: "i386" [DEBUG] Building Maven user-level plugin registry from: '/home/chelck/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/home/chelck/maven-2.0.7/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] [INFO] Building parent pom [INFO]task-segment: [test] [INFO] [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:LATEST [DEBUG] maven-compiler-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-compiler-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1286) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycl e(DefaultLifecycleExecutor.java:1221) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa ppings(DefaultLifecycleExecutor.java:987) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi nVersion(DefaultPluginVersionManager.java:228) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi nVersion(DefaultPluginVersionManager.java:90) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM anager.java:166) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default LifecycleExecutor.java:1257) ... 17 more [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Wed Nov 28 14:52:53 GMT 2007 [INFO] Final Memory: 1M/4M [INFO] --- %<- Thanks, Christopher Helck **