CodeSoh documentation

Appearance

Browse a repository ​

The repository pages show what the repository holds, down to the entries inside a jar. You need read permission.

The tree ​

The repository page opens on a tree of groups. Clicking a group shows the groups under it and the artifacts in it. Each artifact row shows its artifact ID, its latest version, and the name and description from its POM.

The tree shows only groups and artifacts that have files. An artifact whose files were all deleted doesn't appear.

An artifact ​

An artifact page shows the following:

  • The group ID and artifact ID.
  • Every version, newest first, with how many files it has and how much it takes.
  • The name, description, URL, licenses, developers, and dependencies from the POM of the newest version.

A version ​

A version page shows the following:

  • Every file of the version, with its classifier, its extension, and its size.
  • The POM: packaging, name, description, URL, parent, licenses, developers, source control URL, dependencies, and dependency management entries.
  • The Gradle module file's variants, if the version has one. See Gradle Module Metadata.
  • For a jar, whether it's a Maven plugin, with its goal prefix and goals, its OSGi headers, and how many entries it holds.
  • For a snapshot, the builds that were deployed. See Snapshots.

If the version is relocated, the POM's relocation coordinates are shown, so you can see where the artifact moved to.

A file ​

A file page shows the following:

  • The path, the size, and the coordinates.
  • The MD5, SHA-1, SHA-256, and SHA-512 digests.
  • Where the file came from: deployed here, or cached from an upstream. A deployed file names the account or the token that deployed it. A cached file names the upstream, the URL it came from, and which checksums were verified.
  • Whether a detached signature was deployed next to it. See Checksums and signatures.
  • Its provenance: the recorded events for that path, newest first. See Activity.

Inside an archive ​

For a jar, war, ear, aar, or zip, the file page lists the entries with their compressed and uncompressed sizes and their compression method.

Click an entry to open it. Text and images open in your browser; anything else downloads.

Entries are served in a sandbox, so a page inside an archive can't act as Artifex, read your session, or reach the rest of the site.

Read Javadoc ​

A Javadoc jar is an archive like any other, so you can read it in place instead of downloading and extracting it.

To read the Javadoc of a version, follow these steps:

  1. Open the version page.
  2. Open the file whose classifier is javadoc.
  3. In the entry list, open index.html.

The pages link to each other inside the archive, so you can navigate the documentation normally. An entry that uses a compression method other than stored or deflated can't be shown.

Delete ​

Where the repository's settings allow deleting, the file and version pages offer it. Deleting a version deletes every file of that version. For more information, see Immutability.