Package Search build system support limitations

Package Search supports many cases in searching and managing dependencies in your project. However, there are some limitations depending on a build tool used in your project.

Gradle

For Gradle only a top level dependencies { } block is supported in the build script. Dependencies set from other places (such as a subprojects block in the root build script) are not supported. Also note, that Gradle modules without the build.gradle[.kts] file are not currently supported.

Anything not listed in the following table is not supported (but may be in the future).

Use Cases	Support
	Kotlin	Groovy
Full string in dependencies: `“io.ktor:ktor-client-cio:1.6.1”`	read version write version updates in the editor	read version write version updates in the editor
Full string with a direct variable: `val ver = "1.6.1"` `“io.ktor:ktor-client-cio:$ver”`	read version write version updates in the editor	read version write version updates in the editor
Full string with the delegate variable to `gradle.properties`: `“io.ktor:ktor-client-cio:$ver”`	read version write version updates in the editor	read version write version updates in the editor
Ext properties: `ext.ver = “1.6.1”` `“io.ktor:ktor-client-cio:$ver”`	read version write version updates in the editor	read version write version updates in the editor
Split GAV dependency: `implementation group: "io.ktor", name: "ktor-client-apache", version: '1.5.4'`	read version write version updates in the editor	read version write version updates in the editor
Version catalogs (experimental, refer to Gradle documentation.	read version write version updates in the editor	read version write version updates in the editor
Invoke function for version: `implementation("io.ktor:ktor-client-cio:${banana()}")`	read version write version updates in the editor	read version write version updates in the editor

If you encounter any problems with the supported styles, report them to Gradle subsystem.

Maven

All types of dependencies are supported for Maven. All dependencies can be updated if the version is defined using the regular syntax, or it is defined using properties and the ${} syntax. Recursive property declarations (when a property value is defined using another property) are not supported yet.

Use cases	Support
Simple project, the dependency is defined in the file itself: <dependency> <groupId>...</groupId> <artifactId>...</artifactId> <version>...</version> </dependency>	Read Modify A new dependency is created as simple dependency if this dependency is not declared in the parent `<dependencyManagement>` section.
Dependency defined in the parent `<dependencyManagement>` section and is declared in a child section.	Read Modify A new dependency is created as a managed dependency if this dependency declared in the parent `<dependencyManagement>` section.
Dependency declared in the parent section as a dependency and inherited in a project.	Read Modify
Dependency declared in BOM and imported into a project	Read Modify

If you encounter any problems with the supported styles, report them to Maven subsystem.

sbt

Using simple data flow analysis, it is possible to capture some of the common patterns for libraries. However, dependencies with more complex patterns, for example, generated from functions, are not supported.

Use Cases	Support
Inline library dependencies: `libraryDependencies += “org.scalatest” %% “scalatest” % “3.0.8” % Test`	update the version from the editor capture from the tool window modify from the tool window
Library dependencies created using `val`: `val scalatest = “org.scalatest” %% “scalatest” % “3.0.8”` `libraryDependencies += scalatest % Test`	update the version from the editor capture from the tool window modify from the tool window
Sequence of library dependencies: `libraryDependencies ++= Seq(scalatest, scalariform)`	update the version from the editor capture from the tool window modify from the tool window
Library dependencies inside top-level subprojects: `lazy val common = (project in file("common")) .settings( name := "common", scalaVersion := "3.0.0", libraryDependencies += "org.scalatest" %% "scalatest" % "3.2.9" % Test )`	update the version from the editor capture from the tool window modify from the tool window
Library dependencies inside top-level subprojects that are generated by functions: `lazy val common: Project = customNewProject(name=”common”, file(“common”))`	update the version from the editor capture from the tool window modify from the tool window
Library dependencies are generated by functions: `libraryDependencies += generateScalaTestDep(version=”3.0.8”)`	update the version from the editor capture from the tool window modify from the tool window
sbt plugins: `addSbtPlugin("com.typesafe.sbt" % "sbt-site" % "0.7.0")`	update the version from the editor capture from the tool window modify from the tool window

If you encounter any problems with the supported styles, report them to Scala plugin.

Repositories

Only a selection of public Maven repositories is included in the Package Search index. You can check the list of indexed repositories at the Package Search website.

The private Maven repositories are not supported. If you use private Maven repositories and need for Package Search to add support for on-premises instances, upvote this issue. Note that comments are not counted as upvotes.

Private proxies of public repositories are not currently supported. If you use proxies and would like to get support in the Package Search plugin, upvote this issue. Note that comments are not counted as upvotes.

Last modified: 11 February 2024