<activation>
                <file>
                    <exists>simple.xml</exists>
                </file>
                <property>
                    <name>myproperty</name>
                    <value>test</value>
                </property>
            </activation>
            <properties>
                <profile.file>activated-1</profile.file>
            </properties>
        </profile>

    }

    @Test
    void testAndConditionInActivation() throws Exception {
        Properties sysProperties = new Properties();
        sysProperties.setProperty("myproperty", "test");

        ModelBuilder builder = new DefaultModelBuilderFactory().newInstance();
        assertNotNull(builder);

        DefaultModelBuildingRequest request = new DefaultModelBuildingRequest();

  <packaging>pom</packaging>

  <profiles>

    <profile>
      <id>property-name-project-version</id>
      <activation>
        <property>
          <name>${project.version}</name>
        </property>
      </activation>
    </profile>
    <profile>
      <id>property-value-project-version</id>
      <activation>
        <property>
          <name>project.version</name>
          <value>${project.version}</value>

  ** since Maven 3.5.0, if <<<project.directory>>> POM property value is defined, it is used instead of artifact id:
  this permits default inheritance calculations when module directory name is not equal to artifact id. Notice that this
  property is not inherited from a POM to its child: child's POM will use child artifact id if property is not
  set.

		<!-- 
		<property name="parameterKey">"fessRoles"</property>
		<property name="encryptedParameterValue">false</property>
		<property name="headerKey">"fessRoles"</property>
		<property name="encryptedHeaderValue">true</property>
		<property name="cookieKey">"fessRoles"</property>
		<property name="encryptedCookieValue">true</property>
		<property name="cipher">

                                    <div class="form-inline col-sm-9">
                                        <la:errors property="webApiJson"/>
                                        <div class="form-check">
                                            <la:checkbox styleId="webApiJson" styleClass="form-check-input" property="webApiJson"/>
                                            <label for="webApiJson" class="form-check-label">

		<property name="queueIndex">"fess_crawler.queue"</property>
		<property name="queueShards">5</property>
		<property name="queueReplicas">1</property>
		<property name="dataIndex">"fess_crawler.data"</property>
		<property name="dataShards">5</property>
		<property name="dataReplicas">1</property>
		<property name="filterIndex">"fess_crawler.filter"</property>
		<property name="filterShards">5</property>

This is out of scope for this ADR.  Migrating an existing property to lazy types is being handled in a different way.

### Conventions

Once a new property has been introduced, you need to consider what its conventions will be.

                    """
                        package com.example;
                        import org.gradle.api.provider.Property;

                        public abstract class Task {
                            public abstract Property<Boolean> getFailOnError();
                            public Property<Boolean> getIsFailOnError() {
                                return getFailOnError();
                            }

            <la:form action="/admin/scheduler/">
                <la:hidden property="crudMode"/>
                <c:if test="${crudMode==2}">
                    <la:hidden property="id"/>
                    <la:hidden property="versionNo"/>
                </c:if>
                <la:hidden property="createdBy"/>
                <la:hidden property="createdTime"/>
                <div class="row">