more detailed with an example?
>
> Cheers,
>
> Marco
> - Original Message -
> From: <[EMAIL PROTECTED]>
> To: "Maven Users List" <[EMAIL PROTECTED]>
> Sent: Friday, January 23, 2004 7:33 AM
> Subject: Re: Making plugins a dependency
>
Jörg Schaible <[EMAIL PROTECTED]> wrote on 22/01/2004
08:55:26 PM:
[snip]
> You are working offline so the build will continue, but
maven-junit-report-
> plugin-1.4-SNAPSHOT.jar may be out of date!
> Attempting to download xjavadoc-1.0.2.jar.
> WARNING: Failed to download xjavadoc-1.0.2.jar.
st
> Betreff: Re: AW: Making plugins a dependency
>
>
> What platform have you tried this on? I found that the way the 'SSH'
> command is executed on Linux in RC1 is broken. Has anyone else had this
> experience?
>
> --Alex V.
>
> On Thu, 2004-01-22 at 23:50, O
What platform have you tried this on? I found that the way the 'SSH'
command is executed on Linux in RC1 is broken. Has anyone else had this
experience?
--Alex V.
On Thu, 2004-01-22 at 23:50, Oliver Nölle wrote:
> > Could you please be a bit more detailed with an example?
>
> See the message I
> Could you please be a bit more detailed with an example?
See the message I posted before, it's a goal that uses
repository:copy-artifact
Oliver
P.S.
Here is what I wrote:
I wrote the following goal to accomplish what I would have expected a
plugin:deploy goal to do:
Could you please be a bit more detailed with an example?
Cheers,
Marco
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Friday, January 23, 2004 7:33 AM
Subject: Re: Making plugins a dependency
> Use repository:
Use repository:copy-artifact
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Mark R. Diggory" <[EMAIL PROTECTED]> wrote on 23/01/2004
08:58:47 AM:
> But, more specifically, for project external to maven, isn't this just
> the same process as getting yo
...
Oliver
> -Ursprungliche Nachricht-
> Von: Mark R. Diggory [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 22. Januar 2004 22:59
> An: Maven Users List
> Betreff: Re: Making plugins a dependency
>
>
> But, more specifically, for project external to maven, is
at shall I specify in the project.xml file in order
to include my plugin in the project?
Thanks,
Marco
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Users List" <[EMAIL PROTECTED]>
Sent: Thursday, January 22, 2004 11:08 AM
Subject: Réf. : RE: Making plugins a d
That was basically the only feature added to RC1 over beta-10 :) It should
work just fine.
- Brett
> -Original Message-
> From: Eric Pugh [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 22 January 2004 8:37 PM
> To: 'Maven Users List'
> Subject: RE: Making plugins
But, more specifically, for project external to maven, isn't this just
the same process as getting your artifacts published?
http://maven.apache.org/repository-upload.html
goals corresponding to this
dist:deploy
jar:deploy
...
but plugin:deploy ... doesn't exacty do the same thing, now does it?
http://maven.apache.org/reference/developers/releasing-plugins.html
Alex Vollmer wrote:
The 'plugin:install' goal installs the JAR in the local repository, I
want a goal that installs the JAR in the remote repository.
--Alex V.
On Thu, 2004-01-22 at 12:58, Incze Lajos wrote:
On Thu, Jan 22, 20
The 'plugin:install' goal installs the JAR in the local repository, I
want a goal that installs the JAR in the remote repository.
--Alex V.
On Thu, 2004-01-22 at 12:58, Incze Lajos wrote:
> On Thu, Jan 22, 2004 at 11:48:46AM -0800, Alex Vollmer wrote:
> > What Maven goal will allow me to deploy
On Thu, Jan 22, 2004 at 11:48:46AM -0800, Alex Vollmer wrote:
> What Maven goal will allow me to deploy my plugin to our repository the
> same way I would deploy any other kind of artifact? Basically the normal
> 'jar:deploy' puts the JAR file in the 'jars' sub-directory and I want it
> to go into
in advance.
--Alex V.
On Wed, 2004-01-21 at 17:09, Brett Porter wrote:
> Yes. It's a normal dependency, but add plugin.
>
> Cheers,
> Brett
>
> > -Original Message-
> > From: Alex Vollmer [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 22 January
Jörg Schaible wrote:
I try it currently with RC2, but it does not work either:
=== snip===
xdoclet
xjavadoc
1.0.2
http://xdoclet.sourceforge.net
plugin
xdoclet
xdoclet
1.2
http://xdoclet.sourceforge.net
plugin
[...]
PROTECTED]>
22/01/2004 14:00
Veuillez répondre à "Maven Users List"
Pour : "'Maven Users List'" <[EMAIL PROTECTED]>
cc :
Objet : RE: Réf. : RE: Making plugins a dependency
It works just fine but when used with a multiproject setu
ase you run into the
same thing.
Maven-1.0 rc1
Tim Chen
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 6:09 AM
To: Maven Users List
Subject: Réf. : RE: Making plugins a dependency
Xdoclet dependancies are not "plu
ECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 6:09 AM
To: Maven Users List
Subject: Réf. : RE: Making plugins a dependency
Xdoclet dependancies are not "plugin dependancies" but jar dependancies.
To make maven-xdoclet-p
OTECTED]>
22/01/2004 10:55
Veuillez répondre à "Maven Users List"
Pour : "Maven Users List" <[EMAIL PROTECTED]>
cc :
Objet : RE: Making plugins a dependency
Eric Pugh wrote on Thursday, January 22, 2004 10:37 AM:
> Does this work with RC1
Eric Pugh wrote on Thursday, January 22, 2004 10:37 AM:
> Does this work with RC1 of Maven? Or is this something added
> after RC1, and I should wait for RC2 before using heavily?
>
> Eric
I try it currently with RC2, but it does not work either:
=== snip===
> Subject: RE: Making plugins a dependency
>
>
> Yes. It's a normal dependency, but add plugin.
>
> Cheers,
> Brett
>
> > -Original Message-
> > From: Alex Vollmer [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, 22 January 2004 12:00 PM
> > T
Yes. It's a normal dependency, but add plugin.
Cheers,
Brett
> -Original Message-
> From: Alex Vollmer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 22 January 2004 12:00 PM
> To: Maven Users List
> Subject: Making plugins a dependency
>
>
> We have sever
We have several products that are built by Maven that share common Jelly
code in a plugin I've been writing. I'm trying to avoid either
reminding people to do 'plugin:install' everytime there's a change to
the plugin or writing some kind of lame wrapper script around maven to
check for a new plugi
24 matches
Mail list logo