You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nick Stolwijk <ni...@gmail.com> on 2008/11/11 10:32:30 UTC
Re: Default plugin execution id
Hi Rahul,
First of all, welcome to Maven!
The error you encountered is mostly because of a proxy between you and
the central maven repository. To fix this you can enter your proxy
information in your settings.xml [1], which can be found under
$HOME/.m2/settings.xml or $M2_HOME/conf/settings.xml. (The first one
overrides the second one)
Secondly, please don't post to the dev list with user questions. The
dev list is for the development of Maven and the user list for user
questions.
Also, start new messages instead of replying to another thread. This
way mail readers still know which message belongs to which thread.
Hth,
[1] http://maven.apache.org/ref/2.0.9/maven-settings/settings.html
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Tue, Nov 11, 2008 at 9:22 AM, Limkar Rahul
<Ra...@atosorigin.com> wrote:
>
>
> Hi
> I am a new user of Maven. I have downloaded maven. But when I
> run following line at command prompt. I am facing following error.
> Can you please help me.
>
>
> C:\>mvn archetype:create -DarchetypeGroupId=org.apache.maven.archetypes
> -DgroupId=net.roseindia.maven.quickstart -DartifactI
> d=HelloMaven -e
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> ----
> [INFO] Building Maven Default Project
> [INFO] task-segment: [archetype:create] (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> ----
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-3:creat
> e': Cannot find Plexus container for plugin:
> org.apache.maven.plugins:maven-archetype-plugin
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
> in the plugin manager executing goal 'org.apache.maven
> .plugins:maven-archetype-plugin:2.0-alpha-3:create': Cannot find Plexus
> container for plugin: org.apache.maven.plugins:maven-
> archetype-plugin
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
> LifecycleExecutor.java:538)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
> l(DefaultLifecycleExecutor.java:488)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
> ifecycleExecutor.java:458)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures(DefaultLifecycleExecutor.java:306
> )
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:219)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:140)
> 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:256)
> 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: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.PluginManagerException: Cannot find
> Plexus container for plugin: org.apache.maven.plugins:
> maven-archetype-plugin
> at
> org.apache.maven.plugin.DefaultPluginManager.getPluginContainer(DefaultP
> luginManager.java:499)
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPl
> uginManager.java:514)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> nager.java:390)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
> LifecycleExecutor.java:534)
> ... 16 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Tue Nov 11 12:17:36 IST 2008
> [INFO] Final Memory: 1M/3M
> [INFO]
> ------------------------------------------------------------------------
>
> C:\>
>
> Thanks & Regards,
> Rahul Limkar
> System Analyst,
> Pune
> Contact :- +91 020 66755948
>
>
>
> -----Original Message-----
> From: Christian Schulte [mailto:cs@schulte.it]
> Sent: Tuesday, November 11, 2008 12:14 PM
> To: Maven Developers List
> Subject: Re: Default plugin execution id
>
> Brian E. Fox wrote:
>> I think we've gone way off the rails here. I see there's a proposal
> but
>> haven't reviewed it yet.
>>
>> The first portion of this discussion was rather small in scope:
>> Currently default executions of plugins have a null id. The null is
> used
>> to indicate the default config for a plugin across all executions AND
> is
>> used for lifecycle bound or plugins run on the cli. I think we simply
>> should start by separating this. Keep default to replace the current
>> null values for the global plugin configuration as it applies across
> all
>> executions. Then define an id for the lifecycle and cli invocations to
>> be applied to tweak the values as needed (but keeping default to apply
>> across all). Going beyond this into multifaceted ids for packages etc
> is
>> far too complicated imo.
>
> Leads to
>
> <executions>
> <execution>
> <goals>
> <goal>testCompile</goal>
> </goals>
> <configuration>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </execution>
> </executions>
> <configuration>
> <source>1.4</source>
> <target>1.4</target>
> </configuration>
>
> Right ?
>
> Completely hides the lifecycle from the user and removes the need of
> redundant mojo parameters. Minimal input required from the user - Maven
> just does the right thing. At least for this concrete example.
>
> --
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org