### 4. Regenerate Auto-Generated Java Classes

Fess uses DBFlute's LastaFlute FreeGen to automatically generate Java constants from property files.

Run the regeneration command:

```bash
# Option 1: Using Maven from project root
mvn dbflute:freegen

# Option 2: Using DBFlute manage script
cd dbflute_fess
./manage.sh    # On Linux/Mac
manage.bat     # On Windows
# Select option 23 (generate)
```

 *  `M.N`, `M.x` and `master` so we can reliably assume that the leafs of the version tree are unreleased.
 * This convention is enforced by checking the versions we consider to be unreleased against an
 * authoritative source (maven central).
 * We are then able to map the unreleased version to branches in git and Gradle projects that are capable of checking
 * out and building them, so we can include these in the testing plan as well.
 */

	if !regexp.MustCompile(`WHERE .id. = [^ ]+$`).MatchString(stmt.SQL.String()) {
		t.Fatalf("invalid updating SQL, got %v", stmt.SQL.String())
	}

	user3 := *GetUser("save3", Config{})
	DB.Create(&user3)

	if err := DB.First(&User{}, "name = ?", "save3").Error; err != nil {
		t.Fatalf("failed to find created user")
	}

	user3.Name = "save3_"
	if err := DB.Model(User{Model: user3.Model}).Save(&user3).Error; err != nil {

[semver](https://semver.org/) their APIs or accept feature requests for them.
We publish them to maven central because they are dependencies of our plugin
test framework, high level rest client, and jdbc driver but they really aren't
general purpose enough to *belong* in maven central. We're still working out
what to do here.

#### `modules`

            <option value="$PROJECT_DIR$/platforms/software/distributions-publishing" />
            <option value="$PROJECT_DIR$/platforms/software/ivy" />
            <option value="$PROJECT_DIR$/platforms/software/maven" />
            <option value="$PROJECT_DIR$/platforms/software/platform-base" />
            <option value="$PROJECT_DIR$/platforms/software/plugins-distribution" />

    useful for splitting out canceled calls in metrics.

 *  New: Publish a [bill of materials (BOM)][bom] for OkHttp. Depend on this from Gradle or Maven to
    keep all of your OkHttp artifacts on the same version, even if they're declared via transitive
    dependencies. You can even omit versions when declaring other OkHttp dependencies.

    ```kotlin

   * File Specification</a>. Even though the specification only talks about relative urls, absolute
   * urls are actually supported too (for example, in Maven surefire plugin).
   */
  @VisibleForTesting
  static URL getClassPathEntry(File jarFile, String path) throws MalformedURLException {
    return new URL(jarFile.toURI().toURL(), path);
  }

  @VisibleForTesting

Because the release includes breaking API changes, we're changing the project's
package name from `com.squareup.okhttp` to `okhttp3`. This should make it
possible for large applications to migrate incrementally. The Maven group ID
is now `com.squareup.okhttp3`. For an explanation of this strategy, see Jake
Wharton's post, [Java Interoperability Policy for Major Version
Updates][major_versions].

-73.887176513671875 40.818958282470703 -73.917510986328125 40.814346313476563 1 2.01 7.5 0.5 0.5 0 0 8.5 2 1 126 168 green 0.00 2.0 0.0 44 36 6.26 1268 115.02 2 Bronx 011502 2011502 E BX27 Hunts Point 3710 2085 43 2 Bronx 004300 2004300 E BX39 Mott Haven-Port Morris 3710 3389260 2 2014-03-18 10:44:11 2014-03-18 10:50:41 N 1 -73.889472961425781 40.819126129150391 -73.93768310546875 40.838615417480469 1 1.26 6.5 0 0.5 0 0 7 2 1 126 244 green 0.00 0.0 0.0 43 28 6.93 1268 115.02 2 Bronx 011502 2011502...

analysis tool that can measure coverage upon executing specific tests. Eclipse may also be able
to do the same using the EclEmma plugin.

Test coverage reporting used to be possible with JaCoCo when Elasticsearch was using Maven
as its build system. Since the switch to Gradle though, this is no longer possible, seeing as
the code currently used to build Elasticsearch does not allow JaCoCo to recognize its tests.