Page History

...

• Git history
  • fork off new repositories
  • rewrite history
• Shared Maven dependencies / plugin configurations
  • Idea: set up a new parent pom
• Building a common documentation out of many repositories
• End 2 end tests
  • how to share / split tooling
  • In general, tooling will be spread across different repos
• Releases / Versioning / "internal" dependencies
  • a) Single release across all repositories
  • b) Synced releases 
  • c) separate releases
• Requires stable API for downstream projects to rely on (advantage once we have it)
• Higher development friction when debugging Flink problems in downstream projects

Approaches:

• Split into "flink-main" and "flink-connectors"
  • Saves ~1 hour of build time
• One repository, multiple Maven projects

...