<target name="mydbflute.check">
		<condition property="mydbflute.exists">
			<available file="${mydbflute.dir}" type="dir" />
		</condition>
	</target>

	<target name="download.dbflute" depends="mydbflute.check" unless="mydbflute.exists">
		<mkdir dir="${mydbflute.dir}" />
		<get dest="${target.dir}/mydbflute.zip">
			<url url="${mydbflute.url}" />
		</get>

      <version>4.0.0+</version>
      <description>This is the file specification used to activate the profile. The {@code 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, {@code exists} will test for the existence of the file and if it is
        there, the profile will be activated.

      <version>1.0.0+</version>
      <description>
        This is the file specification used to activate a profile. The missing value will be the location
        of a file that needs to exist, and if it doesn't the profile must run.  On the other hand exists will test
        for the existence of the file and if it is there will run the profile.
      </description>
      <fields>
        <field>
          <name>missing</name>

      <!--
          Passes JDK 11-12-specific `no-module-directories` flag to Javadoc tool,
          which is required to make symbol search work correctly in the generated
          pages.

          This flag does not exist on 9-10 and 13+ (https://bugs.openjdk.java.net/browse/JDK-8215582).

          Consider removing it once our release and test scripts are migrated to a recent JDK (17+).
       -->
      <id>javadocs-jdk11-12</id>