I know Im behind a http cache... is that the same as a http proxy? An other observation: Maven doesn't even try to lookup the remote repository (I think). But if I hack the DefaultArtifact version to match the version in my local repository (and not RELEASE), it tries to download that version.
T -----Original Message----- From: Allan Ramirez [mailto:[EMAIL PROTECTED] Sent: 6. januar 2006 09:35 To: Maven Users List Subject: Re: M2: Build error: maven-compiler-plugin does not exist Hi, Please refer to this link http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-HowdoIresolvethe%22%3Cp luginname%3Edoesnotexistornovalidversion%22error%3F -allan Torbjørn Smørgrav wrote: >mvn clean:clean -e -X gives me > >[ERROR] BUILD ERROR >[INFO] -------------------------------------------------------------------- - >------- >[INFO] The plugin 'org.apache.maven.plugins:maven-compiler-plugin' does not >exist or no valid version could be found > >Any suggestions where to look? I get more or less the same >on windows and linux with m2 and m2-alpha2. > >And it worked fine until yesterday. > >The complete output: > >+ Error stacktraces are turned on. >[DEBUG] Building Maven user-level plugin registry from: >'/home/smorgrav/.m2/plugin-registry.xml' >[DEBUG] Building Maven global-level plugin registry from: >'/usr/local/maven/conf/plugin-registry.xml' >[INFO] Scanning for projects... >[INFO] Searching repository for plugin with prefix: 'clean'. >[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:LATEST:pom > > >[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:RELEASE:pom > > >[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(DefaultLif e >cycleExecutor.java:1124) > at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defau l >tLifecycleExecutor.java:1305) > at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggreg a >tionNeeds(DefaultLifecycleExecutor.java:376) > at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl e >Executor.java:132) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9 >) > at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l >.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > 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.resolvePluginVe r >sion(DefaultPluginVersionManager.java:225) > at >org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVe r >sion(DefaultPluginVersionManager.java:87) > at >org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginMana g >er.java:158) > at >org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLif e >cycleExecutor.java:1095) > ... 14 more >[INFO] -------------------------------------------------------------------- - >------- >[INFO] Total time: < 1 second >[INFO] Finished at: Fri Jan 06 10:18:16 GMT 2006 >[INFO] Final Memory: 1M/2M >[INFO] -------------------------------------------------------------------- - >------- > >-----Original Message----- >From: dan tran [mailto:[EMAIL PROTECTED] >Sent: 6. januar 2006 08:54 >To: Maven Users List >Subject: SCM username/password lookup > > >There are 3 places to look for in this order > > Command line > settings.xml > connectionUrl > >However in maven-release-plugin, if user does not provide username >via command line (ie -Dusername=xyz), >username is default to system property ${user.name} and by passing >settings.xml. > >is it a bug? > > >-Dan > > >--------------------------------------------------------------------- >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]
