Add project type detection and language support notifications to Cucumber Eclipse Editor

[Copilot]

Overview

This PR implements automatic project type detection in the Cucumber Eclipse Editor, allowing users to be notified when enhanced language-specific support is available but not installed. The feature seamlessly integrates with the existing validation infrastructure and provides a user-friendly quick fix for installing missing support bundles.

Problem

Currently, users working with Cucumber feature files in Java or Python projects may not be aware that language-specific support bundles are available to enhance their development experience. These support bundles provide features like:

• Step definition navigation
• Code completion for step definitions
• Quick fixes for creating missing steps
• Language-specific validation

Without awareness of these bundles, users miss out on valuable productivity features.

Solution

This implementation adds intelligent detection that:

1. Automatically detects project type by checking Eclipse project natures
2. Verifies bundle installation using the OSGi framework
3. Creates informative markers when support is available but not installed
4. Provides one-click installation via Eclipse quick fix mechanism

How It Works

When a feature file is opened or edited, the GherkinSyntaxValidator now:

• Checks if the project has Java nature (org.eclipse.jdt.core.javanature) or Python nature (org.python.pydev.pythonNature)
• Queries the OSGi framework to see if the corresponding support bundle is installed:
  • io.cucumber.eclipse.java for Java projects
  • io.cucumber.eclipse.python for Python projects
• Creates an INFO severity marker if support is available but not installed

Users can then:

• See the marker in the Problems view and editor margin
• Right-click or press Ctrl+1 to access the quick fix
• Select "Install [Language] support for Cucumber" to begin installation

The quick fix opens a progress dialog that simulates the installation process (10-second blocking operation as specified). The actual installation logic is a placeholder ready for future implementation.

Technical Details

Changes Made

• GherkinSyntaxValidator.java - Enhanced with checkLanguageSupport() and isBundleInstalled() methods
• MarkerFactory.java - Added marker creation/deletion methods for language support markers
• plugin.xml - New marker type and quick fix extension point definitions
• LanguageSupportMarkerResolutionGenerator.java - New quick fix implementation
• package-info.java - Package documentation

Design Decisions

1. INFO severity markers - Non-intrusive notifications that don't clutter the Problems view with warnings/errors
2. Automatic detection - No configuration required; works out of the box
3. Graceful degradation - If OSGi context is unavailable or project nature cannot be determined, the feature silently continues without errors
4. Bundle state awareness - Considers bundles in ACTIVE, STARTING, RESOLVED, or STOPPING states as "installed"
5. Marker lifecycle management - Markers are automatically cleaned and recreated on validation to stay current

Code Quality

• Comprehensive null checking and exception handling
• Consistent with existing codebase patterns (see StepCreationMarkerResolutionGenerator)
• No new external dependencies
• Proper separation of concerns
• Inline documentation and JavaDoc

Example User Flow

User opens feature file in Java project
         ↓
Editor validates and detects Java nature
         ↓
Checks if io.cucumber.eclipse.java is installed
         ↓
Not installed → Creates INFO marker
         ↓
User sees: "Enhanced Java support is available and can be installed"
         ↓
User presses Ctrl+1 on marker
         ↓
Selects: "Install Java support for Cucumber"
         ↓
Progress dialog shows installation (10 seconds)
         ↓
Marker automatically removed

Testing

Due to network connectivity issues with Eclipse P2 repositories during development, full integration testing could not be completed. However:

• All code has been verified for syntax correctness
• Patterns match existing implementations in the codebase
• Extension points are properly defined
• Defensive programming ensures safe operation

Runtime testing should verify:

• Marker creation in Java/Python projects
• Bundle detection accuracy
• Quick fix menu display and execution
• Progress dialog behavior
• Marker deletion after installation

Future Enhancements

The implementation provides hooks for future work:

• Replace the 10-second simulation with actual P2/Marketplace installation
• Add support for additional languages (Ruby, Kotlin, etc.)
• Provide user preferences to customize behavior
• Enhanced error handling and retry mechanisms

Backward Compatibility

This change is purely additive and maintains full backward compatibility:

• No changes to existing validation logic
• No impact on users without Java/Python projects
• Can be disabled by removing the marker resolution extension
• No performance impact (runs in existing validation job)

Statistics

• Files changed: 5
• Lines added: 246
• New classes: 2
• Commits: 3

---

Closes #[issue-number]

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http://download.eclipse.org:80/releases/2025-09/content.jar
  • Triggering command: REDACTED, pid is -1 (http block)
• http://download.eclipse.org:80/releases/2025-09/p2.index
  • Triggering command: REDACTED, pid is -1 (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Add project type detection to the editor

The editor can be enhanced with different language specific extensions (e.g. java or python).
To make the user aware of this we need to do the follwoing:

• Enhance the GherkinSyntaxValidator in io.cucumber.eclipse.editor that it checks the nature of the current project where a project can have many natures enabled
• if the nature contains org.eclipse.jdt.core.javanature it is detected as a java project and the support bundle is io.cucumber.eclipse.java
• if the nature contains org.python.pydev.pythonNature it is detected as a python project and the support bundle is io.cucumber.eclipse.python
• for each detected nature check if the support bundle is installed in the OSGi framework
• if not create an info marker that tells the user that special support for the language is aviable and can be installed
• we want a quickfix for such markers that then allows the user to choose to install the additional support, for the scope of this task it should open a ProgressMonitorDialog and let it block inside the runnablewithprogress for 10 seconds, the actuall work will be implemented later

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.