On Sun, 2003-11-16 at 10:53, Vincent Massol wrote:
> Hi core developers,
> 
> In order to continue our separation of plugins from Maven core, we need
> a way to indicate in a plugin the compatibility it has with other
> artifacts, including other plugins AND with Maven core.
> 
> 1/ For artifacts and plugins, we can use of course the <dependency>
> elements. I believe it could be augmented. For example, a plugin can be
> compatible with several versions of another plugin. So we might want to
> say:
> 
> <dependency>
>   [...]
>   <version>1.5,1.6,2.0</version>
>   [...]
> </dependency>
> 
> The Maven dependency manager would check locally if version 2.0 exists.
> If not, it'll check for 1.6. If not, it'll check for 1.5. If none exist,
> it will try to download version 2.0. If it cannot, it'll try 1.6. etc.
> 
> I believe this is not a very important to implement but still probably
> useful. For the time being we can do without it. However, we need to
> start adding plugin dependencies in our project.xml.

Do we? I think it would be better if the default was that we start
naming plugins in a standard way and using the name of the plugin to
download the latest version of a plugin. Additionally I think a
dependency can be specified if you want to use a particular version.

> 2/ Here's the important part. For the compatibility with Maven core, we
> can't simply add a dependency as downloading the maven jar does not
> replace the full Maven installation. A Maven installation is something
> fixed. Thus we need another way to express this, probably another POM
> tag.
> 
> I'm proposing a top level tag:
> 
> <compatibility>1.0-beta8,1.0-rc1,1.0-rc2-SNAPSHOT</compatibility>

No comma separated lists. Each element must be a specific version or an
expression like 1.4+ which of course means we must start defining a
standard versioning nomenclature.

> Note: Of course, when a plugin is released there should be no SNAPSHOT
> left in the POM. Reminder to self: we need to add this check in the
> famous release plugin.

There is a goal for this already in the release plugin to check.

> In Maven core, the Plugin Manager will check that the installed maven
> version matches the compatibility value.
> 
> If you agree, I'd like to add this <compatibility> tag in POM4 (as a
> mandatory element).
> 
> What do you think?

I think within a plugin POM stating compatibility will probably become
necessary. But I would definitely like to discuss automatic plugin
downloading with the use of consistently named plugins and their goals
and a versioning scheme that can be used by all projects using Maven so
that expressions describing compatability can be meaningful across the
board.

> 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]

Reply via email to