Carlos Sanchez schrieb:

Hi,

You have to setup your repository with
maven.repo.remote=http://www.ibiblio.org/maven,http://your_host/your_dir

That's exactly what I've done.

plugin:download will check in the above appending
/groupId/plugins/artifactId-version.jar

That's exactly the behaviour, when there has been an initial install of the plugin. But it is not the behaviour, if the plugin has never been registered with Maven - it's then looking in /groupId/jars/artifactId-version.jar

BTW: Maven seems to fail at an earlier point, perhaps inside Maven itself, because I could only see the path after setting the -X option.

Here's the stack strace:

File not found on one of the repos
java.io.FileNotFoundException: http://localhost/repository/maven/jars/myplugin-0.1.jar
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:436)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:274)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:170)
at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:317)
at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:254)
at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171)
at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97)
at org.apache.maven.project.Project.verifyDependencies(Project.java:1365)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:492)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
at org.apache.maven.cli.App.doMain(App.java:486)
at org.apache.maven.cli.App.main(App.java:1215)
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 com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)


Kind regards

Peter Nabbefeld


First  http://www.ibiblio.org/maven/groupId/plugins/artifactId-version.jar
Second http://your_host/your_dir/groupId/plugins/artifactId-version.jar

Regards

Carlos Sanchez
A Coru�a, Spain

Oness Project
http://oness.sourceforge.net



-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Peter Nabbefeld
Sent: Sunday, July 11, 2004 2:48 PM
To: [EMAIL PROTECTED]
Subject: Deploying plugins


Hi,

I've tried to write a plugin and deploy it with my local web server (on W2k), placing it in ${docroot}/repository/maven/plugins/myplugin-0.1.jar. Now I've tried to install it using '"%maven_home%\bin\maven" plugin:download -DgroupId=maven -DartifactId=myplugin -Dversion=0.1'. The strange thing is, that it first does not look in the plugins tree, but in the jars tree and fails. I've changed then the name of the directory to jars, but now it looks in plugins. After back-renaming, it works.

The strange thing here is, that Maven obviously looks in jars the first time (and only the first time), then it has learned that the file is a plugin and looks in the plugins tree.

From this all it seems to me, that I'd to put something (possibly a project description?) into the jars tree, and the right destination would probably be the plugins tree.

So my question is: What does Maven expect to find in the jars tree (other than a duplicate of the file)? How do I have to install my plugin an my local server?

Kind regards

Peter Nabbefeld


--------------------------------------------------------------------- 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]



Reply via email to