You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Peter Nabbefeld <Pe...@gmx.de> on 2004/07/11 14:47:53 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Brett Porter <br...@gmail.com>.
Well, the PDF is just the site repackaged, so it should be there..
If you'd like to suggest a change, feel free to post a JIRA bug (under
maven, component documentation), saying the info , where it was in the
PDF/site and where you think it should be.
Thanks,
Brett
On Mon, 12 Jul 2004 06:22:47 +0200, Peter Nabbefeld
<pe...@gmx.de> wrote:
> Brett Porter schrieb:
>
> > where did manual.pdf come from?
> >
> Please excuse me - I've meant maven.pdf - from Maven site.
>
>
>
>
> > On Mon, 12 Jul 2004 03:58:29 +0200, Peter Nabbefeld
> > <pe...@gmx.de> wrote:
> >
> >>Brett Porter schrieb:
> >>
> >>>Do you by any chance have it as a dependency without a type?
> >>>
> >>
> >>Thank You, Brett,
> >>
> >>this has exactly been the problem. Could You add this anywhere on the
> >>web site (users manual)? I've found it - after You told me - in
> >>manual.pdf, but I think it's very basic, so it should probably also
> >>appear on the web.
> >>
> >>Kind regards
> >>
> >>Peter Nabbefeld
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Peter Nabbefeld <Pe...@gmx.de>.
Brett Porter schrieb:
> where did manual.pdf come from?
>
Please excuse me - I've meant maven.pdf - from Maven site.
> On Mon, 12 Jul 2004 03:58:29 +0200, Peter Nabbefeld
> <pe...@gmx.de> wrote:
>
>>Brett Porter schrieb:
>>
>>>Do you by any chance have it as a dependency without a type?
>>>
>>
>>Thank You, Brett,
>>
>>this has exactly been the problem. Could You add this anywhere on the
>>web site (users manual)? I've found it - after You told me - in
>>manual.pdf, but I think it's very basic, so it should probably also
>>appear on the web.
>>
>>Kind regards
>>
>>Peter Nabbefeld
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Brett Porter <br...@gmail.com>.
where did manual.pdf come from?
On Mon, 12 Jul 2004 03:58:29 +0200, Peter Nabbefeld
<pe...@gmx.de> wrote:
> Brett Porter schrieb:
> > Do you by any chance have it as a dependency without a type?
> >
>
> Thank You, Brett,
>
> this has exactly been the problem. Could You add this anywhere on the
> web site (users manual)? I've found it - after You told me - in
> manual.pdf, but I think it's very basic, so it should probably also
> appear on the web.
>
> Kind regards
>
> Peter Nabbefeld
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Peter Nabbefeld <Pe...@gmx.de>.
Brett Porter schrieb:
> Do you by any chance have it as a dependency without a type?
>
Thank You, Brett,
this has exactly been the problem. Could You add this anywhere on the
web site (users manual)? I've found it - after You told me - in
manual.pdf, but I think it's very basic, so it should probably also
appear on the web.
Kind regards
Peter Nabbefeld
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Brett Porter <br...@gmail.com>.
Do you by any chance have it as a dependency without a type?
Anyway, we should be able to figure it out if you post the full output
of maven with -X to JIRA as an attachment after creating an issue.
Thanks,
Brett
On Sun, 11 Jul 2004 20:41:01 +0200, Peter Nabbefeld
<pe...@gmx.de> wrote:
> Carlos Sanchez schrieb:
> > Send the output from Maven using -X
> >
> > Where do you have set maven.repo.remote,
> > in project.properties in your current dir?
> > in build.properties in $HOME?
> >
> >
> project.properties in my current dir.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Peter Nabbefeld <Pe...@gmx.de>.
Carlos Sanchez schrieb:
> Send the output from Maven using -X
>
> Where do you have set maven.repo.remote,
> in project.properties in your current dir?
> in build.properties in $HOME?
>
>
project.properties in my current dir.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Deploying plugins
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Send the output from Maven using -X
Where do you have set maven.repo.remote,
in project.properties in your current dir?
in build.properties in $HOME?
> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Peter Nabbefeld
> Sent: Sunday, July 11, 2004 7:02 PM
> To: users@maven.apache.org
> Subject: Re: Deploying plugins
>
> Carlos Sanchez schrieb:
>
> > Hi,
> >
> > You have to setup your repository with
> >
> maven.repo.remote=http://www.ibiblio.org/maven,http://your_host/your_d
> > ir
> >
> 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(D
> ependencyVerifier.java:254)
> at
> org.apache.maven.verifier.DependencyVerifier.satisfyDependenci
> es(DependencyVerifier.java:171)
> at
> org.apache.maven.verifier.DependencyVerifier.verify(Dependency
> Verifier.java:97)
> at
> org.apache.maven.project.Project.verifyDependencies(Project.java:1365)
> at
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManage
> r.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(NativeMethodAccess
> orImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
> odAccessorImpl.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:news@sea.gmane.org] On Behalf Of Peter Nabbefeld
> >>Sent: Sunday, July 11, 2004 2:48 PM
> >>To: users@maven.apache.org
> >>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: users-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Deploying plugins
Posted by Peter Nabbefeld <Pe...@gmx.de>.
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:news@sea.gmane.org] On Behalf Of Peter Nabbefeld
>>Sent: Sunday, July 11, 2004 2:48 PM
>>To: users@maven.apache.org
>>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: users-unsubscribe@maven.apache.org
>>For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Deploying plugins
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
Hi,
You have to setup your repository with
maven.repo.remote=http://www.ibiblio.org/maven,http://your_host/your_dir
plugin:download will check in the above appending
/groupId/plugins/artifactId-version.jar
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:news@sea.gmane.org] On Behalf Of Peter Nabbefeld
> Sent: Sunday, July 11, 2004 2:48 PM
> To: users@maven.apache.org
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org