solo turn wrote:
thank you!
this is the behaviour i read. i did not understand why it is like that.
* alpha-2:
deployed to default repository without adding anything anywhere.
we found it nice like that.
It's the install mojo
* if we want to deploy the "distributionManagement" sounds ok.
but we do not have "a global repository" for every software.
so we would need to change every pom according to location
and other factors and cannot specify the repository in one
place? can i specify it in settings too, and not in the pom?
or in a "global pom" where i can change it once in a different
location?
You can define a super pom for all your projects and define it as parent
in your projects
Emmanuel
-solo.
On 6/27/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Hi,
you need to define a <repository> in <distributionManagement> in your
pom like this :
<distributionManagement>
<repository>
<id>your_repo_id</id>
<name>Your Repository Name</name>
<url>repository_url</url>
</repository>
</distributionManagement>
and <server> in your settings.xml with the same id like this :
<servers>
<server>
<id>your_repo_id</id>
<username>your_login</username>
</server>
</servers>
Emmanuel
solo turn wrote:
hi,
in the settings.xml i set localRepository. with alpha-3 it deploys to
this repository like before, but it also generates an error:
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error configuring
plugin for execution of 'deploy:deploy'.
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:378)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:129)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103)
at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:269)
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:303)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
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:764)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:527)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
is this an expected behaviour, or where do i specify out "default
deployment repository", so i do not have to put it in every
project.pom?
-solo
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
