How fosorio/egit works
Main Components Overview
a. UI Layer (org.eclipse.egit.ui)
• Provides the user interface components
• Handles user interactions
• Implements views, dialogs, and wizards
b. Core Layer (org.eclipse.egit.core)
• Provides the business logic
• Interfaces with JGit library
• Manages Eclipse workspace integration
c. GitFlow Integration (org.eclipse.egit.gitflow)
• Implements GitFlow workflow support
• Provides GitFlow-specific operations
d. Test Components
• Core tests (org.eclipse.egit.core.test)
• UI tests (org.eclipse.egit.ui.test)
• GitFlow tests (org.eclipse.egit.gitflow.test)
Component Relationships
a. Dependencies:
• UI → Core (UI depends on Core)
• Core → JGit (Core depends on JGit library)
• GitFlow → Core (GitFlow depends on Core)
• GitFlow UI → GitFlow (GitFlow UI depends on GitFlow)
b. Integration Points:
• Eclipse Platform integration
• Workspace resource management
• Team provider implementation
Key Subsystems
Specialized components:
a. Repository Management
• Repository handling
• Git operations (clone, push, pull)
• Branch management
b. Synchronization
• Workspace synchronization
• Resource tracking
• Change management
c. User Interface Components
• Views (History, Staging, Repositories)
• Dialogs and wizards
• Decorators
External Interfaces
Integration with:
a. Eclipse Platform
• Resource management
• Team provider API
• UI extension points
b. JGit Library
• Git operations
• Repository access
Additional Details
Annotations for:
a. Extension Points:
• branchNameProvider
• cloneSourceProvider
• commitMessageProvider
b. Key Services:
• GitProvider
• RepositoryCache
• GitProjectData
c. Important Operations:
• Commit handling
• Branch operations
• Synchronization
Implementation Notes
a. Use a hierarchical layout from top to bottom
b. Keep related components close together
c. Minimize line crossings
e. Version information and dependencies
f. Integration points with Eclipse