It's a bug in 2.0. If it fails the first time, you need to run with -U
to get it to try again.
- Brett
On 11/18/05, Tomas Maven <[EMAIL PROTECTED]> wrote:
> The verbose output I get from running the very first example in the
> Maven "How do I make my first Maven project?" can be found below.
>
> Are there any other options in the setting.xml file I should be aware
> of? The options and values I have set for maven 1.0.2 is the the very
> same I have set for Maven2..
>
> /Tomas
>
> ==============
> C:\build>mvn -e archetype:create -DgroupId=com.mycompany.app
> -DartifactId=my-app
>
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'archetype'.
> [INFO]
> -------------------------------------------------------------------------
> ---
> [ERROR] BUILD ERROR
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
> exi
> st or no valid version could be found
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> 'org.apache.m
> aven.plugins:maven-archetype-plugin' does not exist or no valid version could
> be
> found
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
> ultLifecycleExecutor.java:1124)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor
> (DefaultLifecycleExecutor.java:1356)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListBy
> AggregationNeeds(DefaultLifecycleExecutor.java:376)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> 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-archetype-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:158)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Defa
> ultLifecycleExecutor.java:1095)
> ... 14 more
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: < 1 second
> [INFO] Finished at: Thu Nov 17 14:47:53 CET 2005
> [INFO] Final Memory: 1M/2M
> [INFO]
> -------------------------------------------------------------------------
> ---
>
> 2005/11/17, Jose Gonzalez Gomez <[EMAIL PROTECTED]>:
> > 2005/11/17, Tomas Maven <[EMAIL PROTECTED]>:
> > > Hi, apologies if this question has been posted before.
> > >
> > > I have both maven 1.0.2 and maven 2.0 installed at the same computer
> > > at my office behind a corporate firewall. I have configured my maven
> > > 1.0.2 to handle the proxy, and I'm able to get it to download needed
> > > jar files without any problems. However, when I'm trying to get Maven2
> > > to do the same thing it gives me the
> > > "[WARNING] repository metadata for: 'artifact
> > > org.apache.maven.plugins:maven-archetype-plugin' could not be
> > > retrieved from repository: central due to an error: Error transferring
> > > file" error, which I interpret as it can't get through the firewall.
> > >
> > > For maven 1.0.2 my build.properties in the {user.home} looks like this:
> > > maven.proxy.host=my.proxyhost.domain
> > > maven.proxy.port=8080
> > > maven.proxy.username=scott
> > > maven.proxy.password=tiger
> > >
> > > For Maven2, in my {user.home}.m2 directory I have created a
> > > settings.xml with this content:
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <settings>
> > > <proxies>
> > > <proxy>
> > > <active>true</active>
> > > <protocol>http</protocol>
> > > <host>my.proxyhost.domain</host>
> > > <port>8080</port>
> > > <username>scott</username>
> > > <password>tiger</password>
> > > </proxy>
> > > </proxies>
> > > </settings>
> > >
> > > Any clues or workarounds?
> > > Best regards
> >
> > Have you tried running mvn -e? Maybe you get a more explanatory cause
> > of the error...
> >
> > HTH
> > Jose
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
