eb99f47746
## What Part 2 of https://github.com/airbytehq/airbyte/pull/13122. Follow up to #13476 . Explanation for what is happening: Identically named subprojects have the following issues: * publishing as is leads to classpath confusion when the jars with the same names are placed in the Java distribution. This leads to NoClassDefFound errors on runtime. * deconflicting the jar names without changing directory names leads to dependency errors as the OSS jar pom files are generated using project dependencies (suggesting a dependency a sibling subproject in the same repo) that use subprojects group and name as a reference. This means the generated jars look for Jars that do not exists (as their names have been changed) and cannot compile. * the workaround to changing a subproject's name involves resetting the subproject's name in the settings.gradle and depending on the new name in each build.gradle. This increases configuration burden and decreases the ease of reading, since one will have to check the settings.gradle to know what the right subproject name is. See https://github.com/gradle/gradle/issues/847 for more info. * given that Gradle itself doesn't have support for identically named subprojects (see the linked issue), the simplest solution is to not allow duplicated directories. I've only renamed conflicting directories here to keep things simple. I will create a follow up issues to enforce non-identical subproject names in our builds. * Rename airbyte-config:models to airbyte-config:config-models. * Rename airbyte-config:persistence to airbyte-config:config-persistence.
Tools
Contains various tools (usually bash scripts) to improve quality of life or the build system.
Releasing a new version
Trigger the Github Action Release Open Source Airbyte (https://github.com/airbytehq/airbyte/actions/workflows/release-airbyte-os.yml)
# Merge PR created by the Github Action
git checkout master
git pull --no-rebase
./tools/bin/tag_version.sh