Gradle是否有SQLj插件？Maven转Gradle后如何配置SQLj编译？

Great question! Migrating SQLJ builds from Maven to Gradle is totally doable with a dedicated community plugin, and I’ll walk you through the exact configuration steps to replicate your Maven plugin’s behavior.

First, the go-to Gradle plugin for SQLJ support is the net.linguica.sqlj plugin, which mirrors most of the functionality from the Maven SQLJ plugin. Here’s how to set it up in your build.gradle file:

Step 1: Apply the SQLJ Plugin #

Start by adding the plugin to your Gradle build. This plugin handles SQLJ source compilation out of the box:

plugins {
    id 'java' // Required for Java project support
    id 'net.linguica.sqlj' version '0.9.3' // Use the latest version available
}

Step 2: Configure the SQLJ Compilation Task #

Next, configure the sqlj task to match your Maven plugin setup—this is where you define your source file location, output directory, and compiler arguments:

sqlj {
    // Path to your .sqlj source files (matches Maven's <sourceDirectory>)
    sourceDir = file('src/main/sqlj')
    
    // Directory to output compiled .java and .ser files (matches Maven's <outputDirectory>)
    outputDir = file("$buildDir/generated-sources/sqlj")
    
    // Optional: Add SQLJ compiler arguments (e.g., encoding, database-specific settings)
    compilerArgs = [
        '-encoding', 'UTF-8',
        // Example for Oracle SQLJ: specify the runtime context
        // '-context', 'oracle.sqlj.runtime.OracleSQLJRuntime'
    ]
}

Step 3: Integrate Generated Files into the Build #

You need to tell Gradle to treat the generated .java files as source code and include the .ser files in your final JAR:

sourceSets {
    main {
        java {
            // Add the SQLJ output directory to the Java source set
            srcDir sqlj.outputDir
        }
        resources {
            // Include .ser files (serialized profiles) in the resources
            srcDir sqlj.outputDir
        }
    }
}

Step 4: Add Required Dependencies #

SQLJ requires core API dependencies and a database-specific JDBC/SQLJ runtime. Replace the example below with your database’s dependencies:

dependencies {
    // Core SQLJ API
    implementation 'javax.sql:sqlj-api:1.1'
    
    // Example: Oracle JDBC + SQLJ runtime (adjust for your database)
    implementation 'com.oracle.database.jdbc:ojdbc11:21.13.0.0'
    implementation 'com.oracle.database.sqlj:ojdbc11-sqlj:21.13.0.0'
    
    // For other databases (e.g., DB2, PostgreSQL), use their respective SQLJ dependencies
}

Optional: Ensure Compilation Order #

Make sure the SQLJ compilation runs before the main Java compilation by adding a task dependency:

compileJava.dependsOn(sqlj)

How This Matches Your Maven Setup #

• sourceDir corresponds to Maven’s <sourceDirectory>
• outputDir corresponds to Maven’s <outputDirectory>
• compilerArgs maps to Maven’s <compilerArguments>

If you run into database-specific quirks (like Oracle’s SQLJ requirements), adjust the compilerArgs and dependencies to match your Maven plugin’s configuration.

内容的提问来源于stack exchange，提问作者rinilnath