On Tue, 2002-12-10 at 05:52, Brian Ewins wrote:
> Brian Ewins wrote:
> > [EMAIL PROTECTED] wrote:
> >
> >> Hi Peter
> >>
> >> You could use the maven.xml to 'download' and install a plugin from a
> >> repository if it doesn't exist locally. Or you could ship the plugin
> >> along with the maven.xml and do the install as part of the maven.xml.
> >
> >
> [snip]
> > Please correct me if I'm wrong - after running into this problem on b7,
> > I've been using the 'build with maven' approach on b8 and haven't
> > retested the issue since. I had no replies to questions about this at
> > the time.
>
> Just reading this morning's IRC log, I see Jason has partly answered this:
>
> 1:06:35 AM jason in response to peter donalds request i'm now working on
> a maven plugin artifact
> 1:07:00 AM jason so that project managers/leaders can declare deps on a
> maven plugin and it will be installed transparently for the user.
> 1:08:05 AM jason but i need to clean more stuff up to make that work.
>
> Got a question about this...'project managers/leaders can declare deps
> on a maven plugin' - I have to assume this is somewhere central in the
> maven install, n
No, for project specific plugins they wouldn't be. The plugin artifact
is a new type of artifact that would get pulled down from a remote
repository and installed in ${maven.home}/plugins automatically. So
instead of the artifact going into the local repository it goes into
Maven's repository directory. Starting this started me thinking about
where plugins are actually stored. I'm thinking of a way to keep the
plugins in the local repo as well with a pointer to the plugins
available. The plugins would be expanded in maven's plugin directory but
stored in the local repository.
We discussed having a common set of plugins and users could additionally
add their own if they wish.
> ot on a per-project basis? Otherwise you'd end up with
> eg project 'A' accidentally and irreproducibly building when it depends
> on a plugin the user had previously declared as a dependency of project
> 'B'?
Eventually if a project declares a dependency on a specific version of a
plugin then that's the version that will get used. If the plugins are
stored in the local repository all versions of each of the plugins will
be made available. I'm still working on the plugin revamp. Bare with me.
> Or that we'd have to declare all the plugins we mean to use in a
> project (which takes some of the value away from the centralization in
> maven)
No, we certainly won't have to do that. For a particular version of
maven we will have a certain set of plugins for which you don't have to
specifically declare anything to use them. If you want to override a
specific version or use plugins not provided by maven then you can
speciify what you want. The basics will always be easy but we will
provide a way to customize and hopefully make the use of plugins easy
when customizations are made.
> -Baz
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[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: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
