I've seen this happen before but I'm not entirely sure what causes it...
I've seen people connecting to poorly configured HTTP repositories (which return HTTP 200 and a "Error 404, resource not found" webpage rather than a proper HTTP 404) so I'm curious... What repos are you connecting to, Javier? Or do you know where your troubles originated, if not a bad repo, I'm curious what else it might have been. Obviously this is the kind of thing that Maven needs to be able to recover from more gracefully! Wayne On 1/9/07, JavierL <[EMAIL PROTECTED]> wrote:
I solved the problem maven is going out internet without problems but, apparently, the last plugins update failed and corrupted everything it touched... I deleted maven-install-plugin folder and run mvn install and it worked (and installed mvn plugin correctly). I guess there is a bug in maven... Thanks a lot J Wayne Fay wrote: > > You've got something funky going on. Maven isn't going out to the > Internet to look for these plugins as it should be and your builds are > finishing in 1 second. > > Last time, it was the resources plugin. This time, its the same thing > but the install plugin. > > Do you have a proxy or something? Run mvn -U -cpu -X a couple times > and see if perhaps it doesn't find the plugin and download it > automatically. And/or perhaps check JIRA for this issue -- unsure what > module it would be under, but search for "does not exist" and maybe > you'll find an open issue. > > Wayne > > On 1/9/07, JavierL <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi >> >> It worked with 2.1 version for mvn compile command with my pom. >> >> Nevertheless, I'm having problems to install jta.jar. >> >> If I run C:\work\worldnet21\cinb\trunk>mvn install:install-file >> -DgroupId=javax.transacti >> on -DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar >> -Dfile=\soft\java\jta\jta.1 >> .0.1b.jar -DgeneratePom=false >> >> I got the error: >> >> ----------- >> [INFO] Scanning for projects... >> [INFO] Searching repository for plugin with prefix: 'install'. >> [INFO] >> ------------------------------------------------------------------------- >> --- >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------- >> --- >> [INFO] The plugin 'org.apache.maven.plugins:maven-install-plugin' does >> not >> exist >> or no valid version could be found >> [INFO] >> ------------------------------------------------------------------------- >> --- >> [INFO] For more information, run Maven with the -e switch >> [INFO] >> ------------------------------------------------------------------------- >> --- >> [INFO] Total time: 1 second >> [INFO] Finished at: Tue Jan 09 21:58:39 CET 2007 >> [INFO] Final Memory: 1M/5M >> [INFO] >> ------------------------------------------------------------------------- >> --- >> ------------------ >> >> If can't install jta I can't compile my project... >> >> Any idea ? >> >> >> PS: Sometimes maven use to be a nightmare... >> >> >> >> Wayne Fay wrote: >> > >> > Take a look here: >> > >> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/ >> > >> > As you can see, there are several versions of this artifact available: >> > 2.0, 2.1, and 2.2 being the non-beta versions. >> > >> > In the plugins node of your pom, specify: >> > <plugin> >> > <groupId>org.apache.maven.plugins</groupId> >> > <artifactId>maven-resources-plugin</artifactId> >> > <version>[2.2]</version> >> > </plugin> >> > >> > This will "lock" the version to 2.2. As it seems that Maven is having >> > trouble resolving the LATEST version, locking it to a specify version >> > should perhaps clear up your troubles. If that doesn't work, perhaps >> > try [2.1]. >> > >> > However, Maven should really be able to find and resolve the LATEST >> > version of m-r-p, so it makes me think there's something else going on >> > in your configuration which is breaking things... Or there's a weird >> > bug somewhere in Maven itself that you're running into for some >> > reason. >> > >> > Wayne >> > >> > On 1/9/07, JavierL <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Thanks for your reply. >> >> >> >> I've deleted the folder maven-resources-plugin and the version of >> files >> >> there was 2.2 dated 1/9/2007 8:10:46pm >> >> >> >> I've tried mvn -cpu -X compile and got the error: >> >> >> >> -------------- >> >> C:\work\worldnet21\cinb\trunk>mvn -cpu -X -e compile >> >> + Error stacktraces are turned on. >> >> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents >> and >> >> Settin >> >> gs\jleyba\.m2\plugin-registry.xml' >> >> [DEBUG] Building Maven global-level plugin registry from: >> >> 'c:\maven\bin\..\conf\ >> >> plugin-registry.xml' >> >> [INFO] Scanning for projects... >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [INFO] Building cinb >> >> [INFO] task-segment: [compile] >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [DEBUG] maven-resources-plugin: using locally installed snapshot >> >> [DEBUG] Artifact not found - using stub model: Unable to determine the >> >> latest ve >> >> rsion >> >> >> >> org.apache.maven.plugins:maven-resources-plugin:pom:LATEST >> >> >> >> >> >> [DEBUG] Using defaults for missing POM >> >> org.apache.maven.plugins:maven-resources- >> >> plugin:pom:LATEST >> >> [DEBUG] maven-resources-plugin: using locally installed snapshot >> >> [DEBUG] Artifact not found - using stub model: Unable to determine the >> >> release v >> >> ersion >> >> >> >> org.apache.maven.plugins:maven-resources-plugin:pom:RELEASE >> >> >> >> >> >> [DEBUG] Using defaults for missing POM >> >> org.apache.maven.plugins:maven-resources- >> >> plugin:pom:RELEASE >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [ERROR] BUILD ERROR >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' >> does >> >> not >> >> exi >> >> st or no valid version could be found >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [DEBUG] Trace >> >> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin >> >> 'org.apache.m >> >> aven.plugins:maven-resources-plugin' does not exist or no valid >> version >> >> could be >> >> found >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa >> >> ultLifecycleExecutor.java:1203) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor >> >> (DefaultLifecycleExecutor.java:1436) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForP >> >> ackaging(DefaultLifecycleExecutor.java:975) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycl >> >> eMappings(DefaultLifecycleExecutor.java:941) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau >> >> ltLifecycleExecutor.java:450) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan >> >> dleFailures(DefaultLifecycleExecutor.java:303) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen >> >> ts(DefaultLifecycleExecutor.java:270) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi >> >> fecycleExecutor.java:139) >> >> at >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) >> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) >> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> at >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> >> java:39) >> >> at >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> >> sorImpl.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 p >> >> lugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist >> or >> >> no >> >> val >> >> id version could be found >> >> at >> >> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl >> >> uginVersion(DefaultPluginVersionManager.java:225) >> >> at >> >> org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePl >> >> uginVersion(DefaultPluginVersionManager.java:87) >> >> at >> >> org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPlug >> >> inManager.java:177) >> >> at >> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa >> >> ultLifecycleExecutor.java:1174) >> >> ... 18 more >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- >> >> [INFO] Total time: < 1 second >> >> [INFO] Finished at: Tue Jan 09 20:19:41 CET 2007 >> >> [INFO] Final Memory: 1M/3M >> >> [INFO] >> >> >> ------------------------------------------------------------------------- >> >> --- ------------------------ >> >> >> >> >> >> The error started when I just did a mvn compile. >> >> >> >> Now I wonder how to "specify an older plugin version in your pom with >> >> [1.1.1] style versioning"... >> >> >> >> Thanks in advance >> >> >> >> J >> >> >> >> >> >> >> >> >> >> >> >> >> >> Wayne Fay wrote: >> >> > >> >> > Try mvn -cpu to force an update of your plugins. >> >> > >> >> > If that doesn't work, try mvn -X to enable debug mode and see if >> >> > there's more information provided as to why it won't find and use >> the >> >> > plugin. >> >> > >> >> > Finally, if that doesn't work, I'd dig into the M2 cache/repo on >> your >> >> > local machine and delete the plugins/maven-resources-plugin folder >> and >> >> > then try mvn -cpu again to update the plugins. Before deleting, take >> >> > note of what versions are available in the folder and the timestamps >> >> > on the files. (It might be that a recent release of the resources >> >> > plugin has introduced a bug/regression.) >> >> > >> >> > If it still doesn't work, then I'd file a bug in JIRA with complete >> >> > information on what you've done and perhaps specify an older plugin >> >> > version in your pom with [1.1.1] style versioning to lock Maven to >> >> > that version. At that point, your builds should proceed normally as >> >> > they are using the older plugin version. >> >> > >> >> > Wayne >> >> > >> >> > On 1/9/07, JavierL <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> >> Wayne Fay wrote: >> >> >> > >> >> >> > JTA cannot be provided via Maven due to its licensing. You will >> have >> >> >> > to download it from Sun and install it manually via mvn >> >> >> > install:install-file. >> >> >> > >> >> >> > It might be available from JBoss, Glassfish, Harmony, or Geronimo >> >> >> > under different licensing but you'll need to research this >> yourself. >> >> >> > >> >> >> > Wayne >> >> >> > >> >> >> > On 1/9/07, JavierL <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> >> >> Hi >> >> >> >> >> >> >> >> Since today I'm receiving an error message like this: >> >> >> >> >> >> >> >> --------- >> >> >> >> 'org.apache.maven.plugins:maven-resources-plugin' does not exist >> or >> >> no >> >> >> >> valid >> >> >> >> version could be found >> >> >> >> ------ >> >> >> >> >> >> >> >> when I try to do a mvn compile. >> >> >> >> >> >> >> >> Could please somebody tell me why this problem and how could I >> >> solve >> >> >> it ? >> >> >> >> >> >> >> >> I've searched over the net withou success... >> >> >> >> >> >> >> >> >> >> >> >> Also, I've a project that requires jta.1.0.1b.jar. I've been >> >> looking >> >> >> in >> >> >> >> repos and found just pom files, no jars... I wonder if somebody >> >> knows >> >> >> >> where >> >> >> >> could I found this jar... >> >> >> >> >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> Thanks for your reply. I'll search more to get it. >> >> >> >> >> >> Nevertheless, I couldn't use maven because the error I described in >> my >> >> >> mail... >> >> >> >> >> >> Any idea ? >> >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/plugin-not-found-error-and-jta-tf2947414s177.html#a8244402 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/plugin-not-found-error-and-jta-tf2947414s177.html#a8246242 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > > -- View this message in context: http://www.nabble.com/plugin-not-found-error-and-jta-tf2947414s177.html#a8247088 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
