Jason van Zyl wrote:
plugin:deploy sounds like it should deploy to the remote repo. Is there
no plugin:install for just doing things locally?
General contract was that type:install would deploy the artifact into
the local repository. plugin:install does that, plus it installs the
plugin into
Yes, I would prefer to keep some goal that puts the expanded plugin jar into my
plugin cache only. Call it what you will, but perhaps it could mention
installing the plugin to cache i.e. plugin:install-to-cache or whatever.
The use case is when you are sharing your local repo with other
+1 for rename actual deploy to unpack
+1 for deploy on remote repo
Emmanuel
- Original Message -
From: Vincent Massol [EMAIL PROTECTED]
To: 'Maven Developers List' [EMAIL PROTECTED]
Sent: Thursday, November 27, 2003 9:30 AM
Subject: [Plugin plugin] Changing plugin:deploy
Hi,
I'd
Emmanuel Venisse wrote:
+1 for rename actual deploy to unpack
+1 for deploy on remote repo
ditto.
Did you notice that the plugin:install goal also does something
different than (jar|war|ear):install goals?
What I'd like best would be full suite of deployment goals (install,
install-snapshot,
-Original Message-
From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
Sent: 27 November 2003 15:32
To: Maven Developers List
Subject: Re: [Plugin plugin] Changing plugin:deploy
Emmanuel Venisse wrote:
+1 for rename actual deploy to unpack
+1 for deploy on remote repo
ditto
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: 27 November 2003 17:09
To: Maven Developers List
Subject: Re: [Plugin plugin] Changing plugin:deploy
On Thu, 2003-11-27 at 03:30, Vincent Massol wrote:
Hi,
I'd like to change the plugin:deploy goal so
+1.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 27/11/2003 07:30:23 PM:
Hi,
I'd like to change the plugin:deploy goal so that it deploys the plugin
on the remote repo instead of simply unpacking a plugin
