Further investigation has yielded more interesting results. :-)

In turns out that the maven deploy plugin exception can be made to
occur or not occur simply by the presence of a <profile> in my
~/.m2/settings.xml.

Note that the profile does not even need to be active to trigger the
"missing deploymentRepository" exception, so this seems like a bug
rather than a mis-configuration of my environment.

<settings>
  <profiles>
    <profile>
      <id>corporate</id>
      
      <repositories>
        <repository>
          <id>corporate-central</id>
          <name>Corporate Maven</name>
          <url>http://...</url>
          <layout>legacy</layout>
        </repository>
      </repositories>
      
    </profile>
  </profiles>
</settings>

After further debugging, it turns out that the contents of the
<profile> actually has no impact, its mere presence triggers the bug.

So...

  <profiles>
    <profile/>
  </profiles>

...inside <settings> also triggers the exception during m2 deploy.

Kind Regards,
John Fallows.

On 8/11/05, John Fallows <[EMAIL PROTECTED]> wrote:
> Is there a problem with deployment on the m2 trunk, r231365?
> 
> My project has "pom" packaging, with a <distributionManagement>
> section that contains <repository>, <snapshotRepository> and <site>,
> yet the maven-deploy-plugin deploy:deploy goal still fails with a null
> deploymentRepository parameter.
> 
> See below for pom.xml and stack trace.
> 
> Thanks for any help you can provide.
> 
> Kind Regards,
> John Fallows.
> 
> <project>
>   <modelVersion>4.0.0</modelVersion>
> 
>   <groupId>...</groupId>
>   <artifactId>...</artifactId>
>   <version>...</version>
>   <packaging>pom</packaging>
> 
>   <repositories>
>     <repository>
>       <id>corporate-central</id>
>       <url>http://...</url>
>       <layout>legacy</layout>
>     </repository>
> 
>     <repository>
>       <id>corporate-snapshots</id>
>       <url>http://...</url>
>       <layout>legacy</layout>
>     </repository>
> 
>     <repository>
>       <id>central</id>
>       <url>http://...</url>
>     </repository>
>   </repositories>
> 
>   <pluginRepositories>
>     <pluginRepository>
>       <id>corporate-plugins</id>
>       <url>http://...</url>
>     </pluginRepository>
> 
>     <pluginRepository>
>       <id>central-plugins</id>
>       <url>http://...</url>
>     </pluginRepository>
>   </pluginRepositories>
> 
>   <distributionManagement>
>     <repository>
>       <id>corporate-central</id>
>       <url>scp://...</url>
>       <layout>legacy</layout>
>     </repository>
> 
>     <snapshotRepository>
>       <id>corporate-snapshots</id>
>       <url>scp://...</url>
>     </snapshotRepository>
> 
>     <site>
>       <id>bali-site</id>
>       <url>http://...</url>
>     </site>
>   </distributionManagement>
> </project>
> 
> 
> 
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error configuring plugin for execution of 'deploy:deploy'.
> [INFO] 
> ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error configuring
> plugin for execution of 'deploy:deploy'.
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:342)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:472)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:445)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:431)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:127)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:292)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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.PluginParameterException: Invalid
> or missing parameters: [Mojo parameter [name: 'deploymentRepository';
> alias: 'null']] for mojo:
> org.apache.maven.plugins:maven-deploy-plugin:2.0-alpha-3:deploy
>         at 
> org.apache.maven.plugin.DefaultPluginManager.checkRequiredParameters(DefaultPluginManager.java:782)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:521)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:337)
>         ... 15 more
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to