Initial version based on the IntelliJ plugin

.gitignore

@@ -9,4 +9,6 @@ local.properties
 .settings/
 .loadpath
 .recommenders
-
+target
+.mvn
+.vscode

.project

@@ -20,8 +20,14 @@
 			<arguments>
 			</arguments>
 		</buildCommand>
+		<buildCommand>
+			<name>org.eclipse.m2e.core.maven2Builder</name>
+			<arguments>
+			</arguments>
+		</buildCommand>
 	</buildSpec>
 	<natures>
+		<nature>org.eclipse.m2e.core.maven2Nature</nature>
 		<nature>org.eclipse.pde.PluginNature</nature>
 		<nature>org.eclipse.jdt.core.javanature</nature>
 	</natures>

AGENTS.md

@@ -0,0 +1,113 @@
+# Vaadin Eclipse Plugin - Copilot Integration
+
+## Project Overview
+
+Eclipse plugin providing Copilot integration for Vaadin projects through a REST API interface. The plugin starts an embedded HTTP server that communicates with Vaadin Copilot for AI-assisted development.
+
+## REST API Endpoints
+
+All endpoints receive POST requests with JSON containing:
+- `command`: The operation to perform
+- `projectBasePath`: The project's file system path
+- `data`: Command-specific parameters
+
+### File Operations
+- **write** - Write text content (params: `file`, `content`, `undoLabel`)
+- **writeBase64** - Write binary content as base64 (params: `file`, `content`, `undoLabel`)
+- **delete** - Delete files with undo tracking (params: `file`)
+- **refresh** - Refresh project in workspace
+
+### IDE Integration
+- **showInIde** - Open file in editor (params: `file`, `line`, `column`)
+- **undo/redo** - Perform undo/redo (params: `files` array, returns: `performed`)
+
+### Project Analysis
+- **getVaadinRoutes** - Find @Route annotated classes
+- **getVaadinComponents** - Find Vaadin Component subclasses (params: `includeMethods`)
+- **getVaadinEntities** - Find JPA @Entity classes (params: `includeMethods`)
+- **getVaadinSecurity** - Find Spring Security configurations
+- **getVaadinVersion** - Detect Vaadin version from classpath
+- **getModulePaths** - Get project structure information
+
+### Build & Execution
+- **compileFiles** - Trigger incremental build (params: `files` array)
+- **restartApplication** - Restart launch configurations (params: `mainClass` optional)
+- **reloadMavenModule** - Refresh Maven modules (params: `moduleName` optional)
+- **heartbeat** - Service health check
+
+## Build Commands
+
+```bash
+# Format code (REQUIRED before committing)
+mvn spotless:apply
+
+# Compile only
+mvn clean compile
+
+# Run tests
+mvn clean install
+
+# Skip tests
+mvn clean install -DskipTests
+```
+
+## Implementation Status
+
+### ✅ Completed
+- All core REST endpoints
+- File operations with undo/redo support
+- Binary file handling with base64 encoding
+- Project analysis for Vaadin elements
+- Eclipse IDE integration
+- Comprehensive integration tests
+- New Vaadin Project wizard
+- Hotswap Agent support with JetBrains Runtime
+- Build-time flow-build-info.json generation
+
+### ⚠️ Limitations vs IntelliJ Plugin
+1. **Architecture**: Monolithic switch-based handler vs individual handler classes
+2. **Undo/Redo**: Simple per-file tracking vs IntelliJ's UndoManager integration
+3. **Compilation**: No error tracking service (IntelliJ has CompilationStatusManagerService)
+4. **Endpoint Discovery**: Basic annotation scanning vs microservices framework integration
+5. **Project Events**: Basic open/close listeners vs comprehensive ProjectManagerListener
+6. **Hilla Support**: No @Endpoint/@BrowserCallable detection (IntelliJ has VaadinHillaEndpointsProvider)
+
+## Known Issues
+
+1. **Headless limitations**: Some UI operations don't work in test environment
+2. **No operation batching**: Multiple rapid operations aren't grouped for undo
+3. **Undo/redo in tests**: Operation history context not properly initialized in test environment
+4. **Java project classpath**: VaadinProjectAnalyzer tests fail due to classpath nesting issues
+
+## Testing
+
+### Test Coverage
+- **CopilotRestServiceIntegrationTest** - REST endpoints with real workspace operations
+- **CopilotClientIntegrationTest** - Client-server communication and endpoint contracts
+- **VaadinProjectAnalyzerTest** - Project analysis functionality
+- **NewVaadinProjectWizardTest** - Project creation wizard
+
+Tests run in headless Eclipse environment with temporary workspace creation and automatic cleanup.
+
+## Future Enhancements
+
+### High Priority
+1. Refactor to handler-based architecture
+2. Add compilation status tracking service
+3. Implement operation batching for undo/redo
+4. Add comprehensive unit tests for analyzer and undo manager
+
+### Medium Priority
+1. Add project event listeners for automatic dotfile management
+2. Implement Hilla endpoint discovery
+3. Create centralized error handling service
+4. Add VCS awareness for file operations
+
+## Technical Notes
+
+- **Port**: Dynamically assigned, communicated via dotfiles in `.vaadin/copilot/`
+- **Java Version**: JavaSE-17
+- **Eclipse Target**: 2024-03 release
+- **Key Dependencies**: Eclipse JDT, Debug Core, Gson
+- **Builder**: VaadinBuildParticipant automatically generates flow-build-info.json for projects with Vaadin dependencies
+- **Hotswap**: Requires JetBrains Runtime for hot code replacement support

TESTING.md

@@ -0,0 +1,141 @@
+# Vaadin Eclipse Plugin - Testing Guide
+
+## Test Architecture
+
+The plugin uses a comprehensive testing approach with integration tests that validate the complete REST API functionality against real Eclipse workspace operations.
+
+## Test Organization
+
+Tests are organized as Eclipse test fragments that run within the OSGi runtime environment. This ensures accurate testing of Eclipse-specific functionality including:
+
+- Workspace and resource management
+- Project lifecycle operations
+- Editor integration
+- Build system interactions
+
+## Running Tests
+
+### Maven Build
+```bash
+# Run all tests
+mvn clean install
+
+# Skip tests
+mvn clean install -DskipTests
+
+# Run specific test class
+mvn test -Dtest=TestClassName
+```
+
+### Eclipse IDE
+1. Import project as existing Maven project
+2. Right-click test class → Run As → JUnit Plug-in Test
+3. Tests run in a separate Eclipse runtime workbench
+
+### Manual Testing
+For manual validation of REST endpoints:
+1. Launch Eclipse with the plugin installed
+2. Check console for REST service port
+3. Use REST client tools to test endpoints
+4. Verify operations in Eclipse workspace
+
+## Test Coverage Areas
+
+### Core Functionality
+- REST API endpoint validation
+- File operations (create, read, update, delete)
+- Binary file handling with Base64 encoding
+- Directory structure creation
+- Workspace synchronization
+
+### Integration Points
+- Eclipse resource API integration
+- Java project analysis
+- Build system triggers
+- Editor operations
+- Undo/redo framework
+
+### Error Handling
+- Invalid file paths
+- Project boundary validation
+- Malformed requests
+- Concurrent operation safety
+- Resource cleanup
+
+## Test Best Practices
+
+### Test Isolation
+- Each test creates temporary projects
+- Automatic cleanup after test completion
+- No shared state between tests
+- Random port allocation for REST service
+
+### Validation Approach
+- HTTP status code verification
+- Response content validation
+- File system state verification
+- Eclipse workspace consistency checks
+- Thread safety validation
+
+### Performance Considerations
+- Tests use in-memory workspace when possible
+- Minimal disk I/O for faster execution
+- Parallel test execution where applicable
+- Resource pooling for repeated operations
+
+## Continuous Integration
+
+Tests are designed to run in headless environments:
+- No UI dependencies for core tests
+- Configurable workspace location
+- Exit codes for build system integration
+- XML test reports for CI tools
+
+## Troubleshooting
+
+### Common Issues
+- **OSGi resolution failures**: Check MANIFEST.MF dependencies
+- **Port conflicts**: Service uses dynamic port allocation
+- **Workspace locks**: Ensure proper cleanup in tearDown
+- **Permission errors**: Verify file system permissions
+
+### Debug Options
+```bash
+# Enable verbose logging
+mvn test -Dorg.eclipse.equinox.http.jetty.log.stderr.threshold=DEBUG
+
+# Run with Eclipse console
+-consoleLog -console
+```
+
+## Test Maintenance
+
+### Adding New Tests
+1. Extend appropriate base test class
+2. Use existing test utilities
+3. Follow naming conventions
+4. Document test purpose
+5. Ensure cleanup in tearDown
+
+### Updating Tests
+- Keep tests focused on behavior, not implementation
+- Update tests when API contracts change
+- Maintain backwards compatibility tests
+- Document breaking changes
+
+## Quality Metrics
+
+Target metrics for test suite:
+- Code coverage: >80% for core functionality
+- Test execution time: <5 minutes for full suite
+- Flakiness rate: <1% failure rate
+- Clear failure messages for debugging
+
+## Future Improvements
+
+Planned enhancements to testing infrastructure:
+- Mock framework for external dependencies
+- Performance benchmarking suite
+- Stress testing for concurrent operations
+- Integration with mutation testing tools
+- Automated UI testing with SWTBot

build.target

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<?pde version="3.8"?>
+<target name="Running Platform">
+	<locations>
+		<repository location="https://download.eclipse.org/releases/2024-03" />
+		<location path="${eclipse_home}" type="Profile" />
+	</locations>
+</target>