Skip to content

feat(build): set up two-module structure for framework/batteries split#244

Closed
typotter wants to merge 1 commit intomainfrom
feature/v4-core-upgrade/pr1-module-setup
Closed

feat(build): set up two-module structure for framework/batteries split#244
typotter wants to merge 1 commit intomainfrom
feature/v4-core-upgrade/pr1-module-setup

Conversation

@typotter
Copy link
Collaborator

Summary

Sets up the two-module structure for the v4 SDK upgrade:

  • eppo/ - Framework module (publishes as android-sdk-framework)
  • eppo-android-common/ - Batteries-included module (publishes as android-sdk)

Changes

  • Created eppo-android-common/ module directory structure
  • Updated settings.gradle to include both modules
  • Changed eppo artifact ID to android-sdk-framework
  • Configured publishing for both artifacts

Test Plan

  • Build both modules: ./gradlew assemble
  • Verify framework module publishes without OkHttp/Jackson in final artifact
  • Verify batteries-included module bundles framework code

Part of v4 SDK Upgrade

This is PR 1 of the v4 upgrade series. See AGENT_PROMPT.md for full context.

Create the eppo-android-common module as the batteries-included artifact
while the eppo module becomes the framework artifact. This follows
the same pattern as the common SDK v4 branch.

Changes:
- Create eppo-android-common module with transitive dependency on :eppo
- Update settings.gradle to include new module
- Update example app to depend on :eppo-android-common
- Change eppo module artifact ID from android-sdk to android-sdk-framework
- Use separate namespace for eppo-android-common to avoid BuildConfig conflicts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant