Published artifacts for this plugin are missing <license> block in the pom files

Open
  • Is something wrong?
#190 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
kotlin
Domain
build-system, release

Research direction

Start with the published org/gradle/toolchains/foojay-resolver/1.0.0/foojay-resolver-1.0.0.pom and inspect the plugin's publication configuration. Compare the generated POM with the expected license metadata, then republish or run the available publication checks to confirm the license block is present.

Written by the indexing model from the issue text.

Description

Published artifacts for this plugin are missing block in the pom files.

org/gradle/toolchains/foojay-resolver/1.0.0/foojay-resolver-1.0.0.pom

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <!-- This module was also published with a richer model, Gradle metadata,  -->
  <!-- which should be used instead. Do not delete the following line which  -->
  <!-- is to indicate to Gradle or any Gradle module metadata file consumer  -->
  <!-- that they should prefer consuming it instead. -->
  <!-- do_not_remove: published-with-gradle-metadata -->
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.gradle.toolchains</groupId>
  <artifactId>foojay-resolver</artifactId>
  <version>1.0.0</version>
</project>
Dominant language
Kotlin
Stars
223
Forks
28
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gradle/foojay-toolchains

All issues in gradle/foojay-toolchains

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.