<project path="$PROJECT_DIR$/build-logic-settings/default-settings-plugins" />
                  <project path="$PROJECT_DIR$/build-logic-settings/version-catalogs" />
                </projects>
              </build>
            </builds>
          </compositeBuild>
        </compositeConfiguration>
        <option name="externalProjectPath" value="$PROJECT_DIR$" />

    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]software[/\\]plugins-version-catalog[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-version-catalog",
    "path": "platforms/software/plugins-version-catalog",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "precondition-tester",

errors.storage_file_download_failure=Pobieranie {0} nie powiodło się.
errors.storage_access_error=Błąd dostępu do magazynu: {0}
errors.storage_no_upload_file=Określ plik do przesłania.
errors.storage_directory_name_is_invalid=Nazwa katalogu jest nieprawidłowa.
errors.storage_tags_update_failure=Nie można zaktualizować tagów dla {0}.

success.update_crawler_params = Parametry zaktualizowane.

- we need to deal with plugins as core application logic which can also interact with plugins

* Along with this comes the testing strategies that make this work
* The repository model where plugins can be stored and cataloged
* Bridging this into an OSGi system: if this could be done then we can basically take over p2

TODO

- dealing with processing of input and adapting GAVs before searching i.e. plugin groups in Maven and default searching