complexType "ActivationFile"
Namespace:
Content:
complex, 2 elements
Defined:
globally in maven-4.0.0.xsd; see XML source
Includes:
definitions of 2 elements
Used:
Component Diagram
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (1):
Known Usage Locations
Annotation
version:
4.0.0+
description:
This is the file specification used to activate the profile. The missing value is the location of a file that needs to exist, and if it doesn't, the profile will be activated. On the other hand, exists will test for the existence of the file and if it is there, the profile will be activated.
Variable interpolation for these file specifications is limited to ${basedir}, System properties and request properties.
XML Source (w/o annotations (3); see within schema source)
<xs:complexType name="ActivationFile">
<xs:all>
<xs:element minOccurs="0" name="missing" type="xs:string"/>
<xs:element minOccurs="0" name="exists" type="xs:string"/>
</xs:all>
</xs:complexType>
Content Element Detail (all declarations; defined within this component only; 2/2)
exists
Type:
xs:string, predefined, simple content
version:
4.0.0+
description:
The name of the file that must exist to activate the profile.
XML Representation Summary
<exists>
   
Content: 
{ xs:string }
</exists>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="exists" type="xs:string"/>

missing
Type:
xs:string, predefined, simple content
version:
4.0.0+
description:
The name of the file that must be missing to activate the profile.
XML Representation Summary
<missing>
   
Content: 
{ xs:string }
</missing>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="missing" type="xs:string"/>

XML schema documentation generated with FlexDoc/XML 1.13 using FlexDoc/XML XSDDoc 2.9.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.