<?xml version="1.0" encoding="UTF-8"?>
<project name="dbflute" basedir=".">
	<property name="mydbflute.dir" value="${basedir}/mydbflute" />
	<property name="target.dir" value="${basedir}/target" />
	<property name="branch.name" value="fess-15.2" />
	<property name="mydbflute.url" value="https://github.com/lastaflute/lastaflute-example-waterfront/archive/${branch.name}.zip" />

	<target name="mydbflute.check">
		<condition property="mydbflute.exists">

<?xml version="1.0"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
	<modelVersion>4.0.0</modelVersion>
	<groupId>org.codelibs</groupId>
	<artifactId>corelib</artifactId>
	<packaging>jar</packaging>
	<name>CodeLibs Core Library</name>
	<version>0.7.1-SNAPSHOT</version>

				<configuration>
					<target>
						<ant antfile="${basedir}/dbflute.xml" target="download.dbflute" />
						<ant antfile="${basedir}/module.xml" target="install.modules">
							<property name="with.fess" value="true" />
							<property name="opensearch.version" value="${opensearch.version}" />
						</ant>
						<ant antfile="${basedir}/plugin.xml" target="install.plugins">
							<property name="with.fess" value="true" />

            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-24-and-surefire-version</id>
              <goals>
                <goal>toolchain</goal>

            To properly test this, you need to remove existing toolchains:
            rm -rf ~/.m2/jdks/ ~/.m2/toolchains.xml
            (But don't run that if you have put something into ~/.m2/toolchains.xml yourself.)
            -->
            <execution>
              <id>download-24-and-surefire-version</id>
              <goals>
                <goal>toolchain</goal>

<?xml version="1.0" encoding="UTF-8"?>
<project name="module" basedir=".">
	<property name="modules.dir" value="${basedir}/modules" />
	<property name="target.dir" value="${basedir}/target/modules" />

	<!-- Maven Repository -->
	<property name="maven.snapshot.repo.url" value="https://central.sonatype.com/repository/maven-snapshots" />
	<property name="maven.release.repo.url" value="https://maven.codelibs.org" />
	<property name="opensearch.version" value="3.2.0" />

<?xml version="1.0" encoding="UTF-8"?>
<project name="plugin" basedir=".">
	<property name="plugins.dir" value="${basedir}/plugins" />
	<property name="target.dir" value="${basedir}/target/plugins" />

	<!-- Maven Repository -->
	<property name="maven.snapshot.repo.url" value="https://central.sonatype.com/repository/maven-snapshots" />
	<property name="maven.release.repo.url" value="https://oss.sonatype.org/content/repositories/releases" />

            won't.

            I have one idea for a better approach, but it's painful, and I haven't tested it: We
            could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be
            covered by testModule.gwt.xml. Maybe I'll try it someday.

            [*] https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle#When_multiple_PathPrefix_es_have_the_same_path

    strategy:
      matrix:
        os: [ ubuntu-latest ]
        java: [ 8, 11, 17, 21 ]
        root-pom: [ 'pom.xml', 'android/pom.xml' ]
        include:
          - os: windows-latest
            java: 21
            root-pom: pom.xml
    runs-on: ${{ matrix.os }}
    env:
      ROOT_POM: ${{ matrix.root-pom }}
    steps:

- **Crypto & Security** (`org.codelibs.core.crypto`, `org.codelibs.core.security`) - Basic cryptographic utilities, message digest operations, and secure random generation
- **XML Processing** (`org.codelibs.core.xml`) - XML DOM utilities, SAX parser helpers, and schema validation support
- **SQL Utilities** (`org.codelibs.core.sql`) - JDBC helper methods for result sets, prepared statements, and connection management