Renaming from Minalac to Voxatile

[pyrollo]

Here is a road map for renaming.

TODO

• Update pom.xml
• Rename Java package from com.ignfab.minalac to com.ignfab.voxatile (TO BE DISCUSSED)
• Rename classes:
  • MinalacGenerator -> Voxatile
  • MinalacGeneratorCLI -> VoxatileCLI or CommandLineInterface (TO BE DISCUSSED)
  • MinalacParserModule -> VoxatileParserModule (in ParamParser class)
• Rename all environment variables MINALAC_ to VOXATILE_
• Update documentation (all)
• Update examples
• Update default values:
  • Default world name in GenerationParams

[indyteo]

TL; DR: I suggest renaming com.ignfab.minalac.generator.modules... to fr.ign.voxatile.modules... and com.ignfab.minalac.generator... to fr.ign.voxatile.core....

---

Regarding the Java package name, it was named using the following pattern:

• com.ignfab: Namespace (same as Maven group ID)
• minalac: Global project name
• generator: Specific suffix (to distinguish from other parts of the global project)

Now, things are a little different because minalac was the global project name, with the generator only being a subpart of it, whereas voxatile is dedicated to that "generator" part. But I suggest we keep a similar pattern:

• fr.ign or com.ignfab: Namespace
• voxatile: Project name
• core / modules: Clear separation between core and modules

This means we'll have fr.ign.voxatile.core.Voxatile on one side, and fr.ign.voxatile.modules.luanti.LuantiOutputModule on the other side, for example.

Proposed structure:

fr.ign.voxatile
├── core
│   ├── exceptions
│   ├── generation
│   │   └── heightmaps
│   │       └── ...
│   ├── inputs
│   ├── models
│   │   └── filters
│   └── ...
└── modules
    ├── luanti
    └── minecraft

Regarding fr.ign vs com.ignfab, if using fr.ign has no serious implication like having to request validation from a lot of people who are not involved in the project, we might want to adopt it now to avoid another possible package name change in the future. Otherwise, keeping com.ignfab seems fine, although it appears that the ignfab.com domain does not exist anymore (and thus might cause issue when trying to use it on the Maven central repository).

Note that if we use fr.ign, we should reflect it in the Maven group ID.