lateinit var buildType: BaseGradleBuildType

    private val steps = BuildSteps()

    private val buildModel =
        CIBuildModel(
            projectId = "Gradle_Check",
            branch = VersionedSettingsBranch("master"),
            buildScanTags = listOf("Check"),
            subprojects = JsonBasedGradleSubprojectProvider(File("../.teamcity/subprojects.json")),
        )

    @BeforeEach

```

## Contributing

1. Fork the repository
2. Create a feature branch: `git checkout -b feature/amazing-feature`
3. Follow coding standards: `mvn formatter:format`
4. Add tests for new functionality
5. Ensure all tests pass: `mvn test`
6. Check license headers: `mvn license:format`
7. Commit changes: `git commit -m 'Add amazing feature'`
8. Push to branch: `git push origin feature/amazing-feature`
9. Open a Pull Request

When adding links which point to resources within git repositories, like
KEPs or supporting documentation, please reference a specific commit and avoid
linking directly to the master branch. This ensures that links reference a
specific point in time, rather than a document that may change over time.

                    ":$performanceProjectName:$taskName",
                    extraParameters =
                        listOf(
                            "-Porg.gradle.performance.branchName" to "%teamcity.build.branch%",
                            "-Porg.gradle.performance.db.url" to "%performance.db.url%",
                            "-Porg.gradle.performance.db.username" to "%performance.db.username%",

### Development Workflow
1. **Fork** the repository on GitHub
2. **Create** your feature branch: `git checkout -b feature/amazing-feature`
3. **Follow** the coding standards: `mvn formatter:format`
4. **Add** comprehensive tests for new functionality
5. **Commit** your changes: `git commit -m 'Add amazing feature'`
6. **Push** to the branch: `git push origin feature/amazing-feature`
7. **Submit** a Pull Request with detailed description

          - os: windows-latest
            java: 21
            root-pom: pom.xml
    runs-on: ${{ matrix.os }}
    env:
      ROOT_POM: ${{ matrix.root-pom }}
    steps:
      # Cancel any previous runs for the same branch that are still running.
      - name: 'Cancel previous runs'
        uses: styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa # 0.12.1
        with:
          access_token: ${{ github.token }}

 * You can get the JSON file as an artifacts of the "autoUpdateTestSplitJsonOnGradleMaster" pipeline in TeamCity.
 */
fun main() {
    val model =
        CIBuildModel(
            projectId = "Check",
            branch = VersionedSettingsBranch("master"),
            buildScanTags = listOf("Check"),
            subprojects = JsonBasedGradleSubprojectProvider(File("./subprojects.json")),
        )

@Deprecated
public class DefaultWagonManager extends org.apache.maven.repository.legacy.DefaultWagonManager
        implements WagonManager {

    // NOTE: This must use a different field name than in the super class or IoC has no chance to inject the loggers
    @Inject
    private Logger log;

    @Inject
    private LegacySupport legacySupport;

    @Inject
    private SettingsDecrypter settingsDecrypter;

    @Inject

import java.io.File

class BuildTypeTest {
    init {
        DslContext.initForTest()
    }

    private val buildModel =
        CIBuildModel(
            projectId = "Gradle_Check",
            branch = VersionedSettingsBranch("master"),
            buildScanTags = listOf("Check"),
            subprojects = JsonBasedGradleSubprojectProvider(File("../.teamcity/subprojects.json")),
        )

    @Test

## Contributing

We welcome contributions to Fess Crawler! Please follow these guidelines:

1. **Fork** the repository
2. **Create** a feature branch (`git checkout -b feature/amazing-feature`)
3. **Commit** your changes (`git commit -m 'Add amazing feature'`)
4. **Push** to the branch (`git push origin feature/amazing-feature`)
5. **Open** a Pull Request

### Development Setup

```bash
# Clone the repository