<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="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();
                            }

    /**
     * Get the value of property as {@link String}.
     * @param propertyKey The key of the property. (NotNull)
     * @return The value of found property. (NotNull: if not found, exception)
     * @throws ConfigPropertyNotFoundException When the property is not found.
     */
    String get(String propertyKey);

    /**
     * Is the property true?

    /**
     * Searches for the property with the specified key in this property list.
     *
     * @param key the property key.
     * @return the value in this property list with the specified key value.
     */
    public String getProperty(String key) {
        return this.get(key);
    }

    /**
     * Searches for the property with the specified key in this property list. If the key is not found in this property

	"os"
	"path/filepath"
	"reflect"
	"testing"
)

type TestItem struct {
	Name     string `json:"Name"`
	Property string `json:"property"`
}

var (
	// TestDir
	queueDir = filepath.Join(os.TempDir(), "minio_test")
	// Sample test item.
	testItem = TestItem{Name: "test-item", Property: "property"}
	// Ext for test item
	testItemExt = ".test"
)

// Initialize the queue store.