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.

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>

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.

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?

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to