Set Up Local SBT Repositories

JFrog Artifactory Documentation

Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

A local SBT repository is used as a target to which you can deploy the output of your build.sbt script. To create an SBT repository, from the Administration module, under Repositories | Repositories | Local, set the Package Type to SBT.

sbt_local_rep.png

When setting up a repository in JFrog Artifactory for SBT packages, the sbt-default layout is automatically selected if no other layout is specified.

SBT Default

  • Layout Namesbt-default

  • Description: This layout is automatically applied when creating a repository without specifying a layout.

  • Limitations: Not supported for cleanup and archiving. The sbt-default layout is not suitable for resolving artifacts during cleanup/archive activities.

  • Recommendation: Avoid using this layout. Instead, opt for alternative layouts that are designed for better artifact management.

Recommended Repository Layouts

We recommend using the following layouts for the best effective dependency management, archive and cleanup processes.

  • Maven Layout

    • Layout Namemaven-2-default

    • Description: Designed for Maven projects.

    • Recommended Action: Choose this layout when working with Maven to ensure proper handling of artifacts, seamless dependency resolution and resolving artifacts during cleanup/archive activities.

  • Ivy Layout

    • Layout Namesbt-ivy-default

    • Description: Designed for Ivy projects.

    • Recommended Action: Choose this layout when working with Ivy to ensure proper handling of artifacts, seamless dependency resolution and resolving artifacts during cleanup/archive activities.

Note

If you have configured repositories with the sbt-default layout, it is recommended to edit these repositories and apply one of the recommended layouts.

Recalculate Index: After changing the layout of a repository, recalculate the index. This step is crucial for indexing artifacts and calculating metadata for all uploaded packages, which in turn optimizes performance during artifact resolution and enhances cleanup and archiving processes.