Re: [Plugin plugin] Changing plugin:deploy
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 developers and you are testing a new plugin that you don't want to make available to others in the local repo. -Peter Vincent Massol wrote: 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 jar in the local plugin cache (if this feature is used by anyone, I can rename the goal to plugin:unpack) Ok? Thanks -Vincent - 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]
Re: [Plugin plugin] Changing plugin:deploy
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 :install would deploy the artifact into the local repository. plugin:install does that, plus it installs the plugin into MAVEN_HOME/plugins. This may be confusing by intself. I hope that plugin:install plugin:install-snapshot plugin:deploy plugin:deploy-snapshot will act consistently with the other aftifact handling plugins in the future. As for deploying the plugin into MAVEN_HOME/plugins, I feel it should be handled speparately - but what about the name? enable activate setup (suggested by Vincent) insert (think kernel modules) R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Plugin plugin] Changing plugin:deploy
+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 jar in the local > plugin cache (if this feature is used by anyone, I can rename the goal > to plugin:unpack) > > Ok? > > Thanks > -Vincent > > > - > 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]
RE: [Plugin plugin] Changing plugin:deploy
> -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 that it deploys the plugin > > on the remote repo instead of simply unpacking a plugin jar in the local > > plugin cache (if this feature is used by anyone, I can rename the goal > > to plugin:unpack) > > plugin:deploy sounds like it should deploy to the remote repo. Is there > no plugin:install for just doing things locally? That's the point... plugin:deploy is not doing what you thought it would be doing (hence my proposal to rename it)... There is a plugin:install for doing things locally. plugin:deploy is currently unpacking the plugin jar locally. > > > Ok? > > +1 > > > Thanks > > -Vincent > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > http://tambora.zenplex.org > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > - > 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]
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 that it deploys the plugin > on the remote repo instead of simply unpacking a plugin jar in the local > plugin cache (if this feature is used by anyone, I can rename the goal > to plugin:unpack) plugin:deploy sounds like it should deploy to the remote repo. Is there no plugin:install for just doing things locally? > Ok? +1 > Thanks > -Vincent > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Plugin plugin] Changing plugin:deploy
> -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. > > 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, deploy, deploy-snapshot) working consistently with > the plugins for other artifact types. > > There is a problem though with the current plugin:install goal: there > must be a goal for deploying the plugin into maven runtime, which is > different that deploying into local/remote directory. How should this > one be called? Ideas, anyone? plugin:setup ? plugin:install-maven ? However, maybe we can simply keep plugin:install which will do 2 things: - install the plugin as an artifact in the local repo - install it in maven -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Plugin plugin] Changing plugin:deploy
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, deploy, deploy-snapshot) working consistently with the plugins for other artifact types. There is a problem though with the current plugin:install goal: there must be a goal for deploying the plugin into maven runtime, which is different that deploying into local/remote directory. How should this one be called? Ideas, anyone? R. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Plugin plugin] Changing plugin:deploy
+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 like to change the plugin:deploy goal so that it deploys the plugin > on the remote repo instead of simply unpacking a plugin jar in the local > plugin cache (if this feature is used by anyone, I can rename the goal > to plugin:unpack) > > Ok? > > Thanks > -Vincent > > > - > 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]
