2005-05-31 12:24:34 -04:00
|
|
|
<model>
|
|
|
|
<id>profiles</id>
|
|
|
|
<name>Profiles</name>
|
|
|
|
<description><![CDATA[
|
|
|
|
Project-local overrides to the build process based on detected or user-provided environmental parameters.
|
|
|
|
This is the model specification for ${basedir}/profiles.xml.
|
|
|
|
]]></description>
|
|
|
|
<defaults>
|
|
|
|
<default>
|
|
|
|
<key>package</key>
|
2005-05-31 17:48:55 -04:00
|
|
|
<value>org.apache.maven.profiles</value>
|
2005-05-31 12:24:34 -04:00
|
|
|
</default>
|
|
|
|
</defaults>
|
|
|
|
<classes>
|
|
|
|
<class rootElement="true" xml.tagName="profilesXml">
|
|
|
|
<name>ProfilesRoot</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description>Root element of the profiles.xml file.</description>
|
|
|
|
<fields>
|
|
|
|
<field>
|
|
|
|
<name>profiles</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
Configuration of build profiles for adjusting the build
|
|
|
|
according to environmental parameters
|
|
|
|
]]></description>
|
|
|
|
<association>
|
|
|
|
<type>Profile</type>
|
|
|
|
<multiplicity>*</multiplicity>
|
|
|
|
</association>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>activeProfiles</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
List of manually-activated build profiles, specified in the order in which
|
|
|
|
they should be applied.
|
|
|
|
]]></description>
|
|
|
|
<association>
|
|
|
|
<type>String</type>
|
|
|
|
<multiplicity>*</multiplicity>
|
|
|
|
</association>
|
|
|
|
</field>
|
|
|
|
</fields>
|
|
|
|
</class>
|
|
|
|
<class>
|
|
|
|
<name>Profile</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
Modifications to the build process which is keyed on some
|
|
|
|
sort of environmental parameter.
|
|
|
|
]]></description>
|
|
|
|
<fields>
|
|
|
|
<field>
|
|
|
|
<name>id</name>
|
|
|
|
<required>true</required>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<type>String</type>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description>The ID of this build profile, for activation
|
2005-05-31 12:24:34 -04:00
|
|
|
purposes.</description>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>activation</name>
|
|
|
|
<version>1.0.0</version>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description><![CDATA[The conditional logic which will automatically
|
2005-05-31 12:24:34 -04:00
|
|
|
trigger the inclusion of this profile.]]></description>
|
|
|
|
<association>
|
|
|
|
<type>Activation</type>
|
|
|
|
</association>
|
|
|
|
</field>
|
|
|
|
<field>
|
2005-06-07 23:27:43 -04:00
|
|
|
<name>properties</name>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description>Extended configuration specific to this profile goes
|
2005-05-31 12:24:34 -04:00
|
|
|
here.</description>
|
2005-06-07 23:27:43 -04:00
|
|
|
<type>Properties</type>
|
|
|
|
<association xml.mapStyle="inline">
|
|
|
|
<type>String</type>
|
|
|
|
<multiplicity>*</multiplicity>
|
|
|
|
</association>
|
2005-05-31 12:24:34 -04:00
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>repositories</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[The lists of the remote repositories]]>
|
2005-06-21 01:42:35 -04:00
|
|
|
</description>
|
2005-05-31 12:24:34 -04:00
|
|
|
<association>
|
|
|
|
<type>Repository</type>
|
|
|
|
<multiplicity>*</multiplicity>
|
|
|
|
</association>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>pluginRepositories</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
The lists of the remote repositories for discovering plugins
|
|
|
|
]]></description>
|
|
|
|
<association>
|
|
|
|
<type>Repository</type>
|
|
|
|
<multiplicity>*</multiplicity>
|
|
|
|
</association>
|
2005-06-21 01:42:35 -04:00
|
|
|
<comment><![CDATA[ This may be removed or relocated in the near
|
|
|
|
future. It is undecided whether plugins really need a remote
|
2005-05-31 12:24:34 -04:00
|
|
|
repository set of their own. ]]></comment>
|
|
|
|
</field>
|
|
|
|
</fields>
|
|
|
|
</class>
|
|
|
|
<class>
|
|
|
|
<name>Activation</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
2005-06-21 01:42:35 -04:00
|
|
|
The conditions within the build runtime environment which will trigger
|
2005-05-31 12:24:34 -04:00
|
|
|
the automatic inclusion of the parent build profile.
|
|
|
|
]]></description>
|
|
|
|
<fields>
|
|
|
|
<field>
|
|
|
|
<name>jdk</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<type>String</type>
|
|
|
|
<description><![CDATA[
|
|
|
|
Specifies that this profile will be activated when a matching JDK is detected.
|
|
|
|
]]></description>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>property</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
Specifies that this profile will be activated when this System property is specified.
|
|
|
|
]]></description>
|
2005-06-07 18:36:44 -04:00
|
|
|
<association>
|
|
|
|
<type>ActivationProperty</type>
|
|
|
|
</association>
|
2005-05-31 12:24:34 -04:00
|
|
|
</field>
|
|
|
|
</fields>
|
|
|
|
</class>
|
|
|
|
<class>
|
|
|
|
<name>Repository</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
Repository contains the information needed
|
|
|
|
for establishing connections with remote repoistory
|
|
|
|
]]></description>
|
|
|
|
<fields>
|
|
|
|
<field>
|
|
|
|
<name>id</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
A unique identifier for a repository.
|
|
|
|
]]></description>
|
|
|
|
<type>String</type>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>name</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
Human readable name of the repository
|
|
|
|
]]></description>
|
|
|
|
<type>String</type>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>url</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
The url of the repository
|
|
|
|
]]></description>
|
|
|
|
<type>String</type>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>snapshotPolicy</name>
|
|
|
|
<version>1.0.0</version>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description>The policy for downloading snapshots - can be "always",
|
|
|
|
"daily" (default), "interval:XXX" (in minutes) or "never".
|
|
|
|
</description>
|
2005-05-31 12:24:34 -04:00
|
|
|
<type>String</type>
|
|
|
|
<defaultValue>daily</defaultValue>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>layout</name>
|
|
|
|
<version>1.0.0</version>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description>The type of layout this repository uses for locating and
|
2005-05-31 12:24:34 -04:00
|
|
|
storing artifacts - can be "legacy" or "default".</description>
|
|
|
|
<type>String</type>
|
|
|
|
<defaultValue>default</defaultValue>
|
|
|
|
</field>
|
Resolving issue: MNG-339
o Added checksumPolicy to artifact repository construction, which meant changing all the places where the factory was called.
o Added two command-line switches (-C=strict-checksum-checking, -c=lax-checksum-checking, or warning)
o Added checksum policy to all repository definitions (profiles.mdo, settings.mdo, maven.mdo)
o Changed the maven-artifact-ant stuff to use a Repository definition with checksumPolicy added to it
NOTE: I just realized that I haven't touched the inheritance/conversion of repository stuff from profiles/settings.xml to the model. I'll do this, and commit the additional changes.
Currently, the default checksum policy is to warn, since there are still bad checksums out there that prevent bootstrapping. Once we chase these down, we can change to default-strict checking. When verifying checksums, SHA-1 is attempted first, with MD5 acting as a backup verification method. If the checksum verification fails legitimately (not related to the process of retrieving/reading the checksum file), then the verification process is repeated ONCE ONLY.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@191536 13f79535-47bb-0310-9956-ffa450edef68
2005-06-20 14:53:53 -04:00
|
|
|
<field>
|
|
|
|
<name>checksumPolicy</name>
|
|
|
|
<version>1.0.0</version>
|
2005-06-21 01:42:35 -04:00
|
|
|
<description>What to do when verification of an artifact checksum fails - warn, fail, etc. Valid values are
|
|
|
|
"fail" or "warn"</description>
|
Resolving issue: MNG-339
o Added checksumPolicy to artifact repository construction, which meant changing all the places where the factory was called.
o Added two command-line switches (-C=strict-checksum-checking, -c=lax-checksum-checking, or warning)
o Added checksum policy to all repository definitions (profiles.mdo, settings.mdo, maven.mdo)
o Changed the maven-artifact-ant stuff to use a Repository definition with checksumPolicy added to it
NOTE: I just realized that I haven't touched the inheritance/conversion of repository stuff from profiles/settings.xml to the model. I'll do this, and commit the additional changes.
Currently, the default checksum policy is to warn, since there are still bad checksums out there that prevent bootstrapping. Once we chase these down, we can change to default-strict checking. When verifying checksums, SHA-1 is attempted first, with MD5 acting as a backup verification method. If the checksum verification fails legitimately (not related to the process of retrieving/reading the checksum file), then the verification process is repeated ONCE ONLY.
git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@191536 13f79535-47bb-0310-9956-ffa450edef68
2005-06-20 14:53:53 -04:00
|
|
|
<type>String</type>
|
|
|
|
<defaultValue>warn</defaultValue>
|
|
|
|
</field>
|
2005-05-31 12:24:34 -04:00
|
|
|
</fields>
|
|
|
|
<codeSegments>
|
|
|
|
<codeSegment>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<code><![CDATA[
|
|
|
|
public boolean equals( Object obj )
|
|
|
|
{
|
|
|
|
Repository other = ( Repository ) obj;
|
|
|
|
|
|
|
|
boolean retValue = false;
|
|
|
|
|
|
|
|
if ( id != null )
|
|
|
|
{
|
|
|
|
retValue = id.equals( other.id );
|
|
|
|
}
|
|
|
|
|
|
|
|
return retValue;
|
|
|
|
}
|
|
|
|
]]></code>
|
|
|
|
</codeSegment>
|
|
|
|
</codeSegments>
|
|
|
|
</class>
|
2005-06-07 18:36:44 -04:00
|
|
|
<class>
|
|
|
|
<name>ActivationProperty</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<description><![CDATA[
|
|
|
|
This is the property specification used to activate a profile. If the value field is empty,
|
|
|
|
then the existence of the named property will activate the profile, otherwise it does a case-sensitive
|
|
|
|
match against the property value as well.
|
|
|
|
]]></description>
|
|
|
|
<fields>
|
|
|
|
<field>
|
|
|
|
<name>name</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<type>String</type>
|
|
|
|
<required>true</required>
|
|
|
|
<description>The name of the property to be used to activate a profile</description>
|
|
|
|
</field>
|
|
|
|
<field>
|
|
|
|
<name>value</name>
|
|
|
|
<version>1.0.0</version>
|
|
|
|
<type>String</type>
|
|
|
|
<description>The value of the property to be used to activate a profile</description>
|
|
|
|
</field>
|
|
|
|
</fields>
|
|
|
|
</class>
|
2005-05-31 12:24:34 -04:00
|
|
|
</classes>
|
|
|
|
</model>
|