o adding <plugins/> element to the model that will be used for configuring

plugins (i am getting tired of the -Dfoo=bar mucking).


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163178 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2004-10-01 14:36:23 +00:00
parent 22f5fe58dc
commit 3ec86ab1ea
1 changed files with 49 additions and 1 deletions

View File

@ -205,7 +205,6 @@
<type>String</type>
<comment>This naming is inconsistent and distribution should occur from a repository structure.</comment>
</field>
<field>
<name>repositories</name>
<version>4.0.0</version>
@ -225,6 +224,15 @@
</association>
<comment>This may be removed or relocated in the near future. It is undecided whether plugins really need a remote repository set of their own.</comment>
</field>
<field>
<name>plugins</name>
<version>4.0.0</version>
<description>Plugin declarations and configuration.</description>
<association>
<type>Plugin</type>
<multiplicity>*</multiplicity>
</association>
</field>
<field>
<name>mailingLists</name>
<version>3.0.0+</version>
@ -1622,6 +1630,46 @@
<fields></fields>
</class>
<!--
<plugins>
<plugin>
<id>plexus</id>
<configuration>
</configuration>
</plugin>
</plugins>
-->
<class>
<name>Plugin</name>
<version>4.0.0</version>
<fields>
<field>
<name>id</name>
<version>4.0.0</version>
<type>String</type>
<required>true</required>
</field>
<field>
<name>version</name>
<version>4.0.0</version>
<required>true</required>
<description>The version of the plugin to be used.</description>
<type>String</type>
</field>
<field>
<name>configuration</name>
<type>Properties</type>
<association xml.mapStyle="inline">
<type>String</type>
<multiplicity>*</multiplicity>
</association>
</field>
</fields>
</class>
<!-- @todo should modello take a parameter/code segment that will forbid the
specification of this in a project other than the user pom? -->
<class>