Jitpack-generated POM XMLs are missing nodes: name, description, url, licenses, developers, scm, inceptionYear

Zhuinden commented 1 year ago

Describe the bug Jitpack-generated POM XMLs are missing nodes: name, description, url, licenses, developers, scm, inceptionYear.

To Reproduce Execute build.

Expected behavior POM xml should have format same as my library's 2.7.0 version.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<!--  do_not_remove: published-with-gradle-metadata  -->
<modelVersion>4.0.0</modelVersion>
<groupId>com.github.Zhuinden</groupId>
<artifactId>simple-stack</artifactId>
<version>2.7.0</version>
<packaging>aar</packaging>
<name>Zhuinden/simple-stack</name>
<description>[ACTIVE] Simple Stack, a backstack library / navigation framework for simpler navigation and state management (for fragments, views, or whatevers).</description>
<url>https://github.com/Zhuinden/simple-stack</url>
<inceptionYear>2017</inceptionYear>
<licenses>
<license>
<name>Apache License 2.0</name>
<url>https://api.github.com/licenses/apache-2.0</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>Zhuinden</id>
<name>Gabor Varadi</name>
<email>zhuinden@gmail.com</email>
</developer>
</developers>
<scm>
<connection>scm:git://github.com/Zhuinden/simple-stack.git</connection>
<developerConnection>scm:git://github.com/Zhuinden/simple-stack.git</developerConnection>
<url>git://github.com/Zhuinden/simple-stack.git</url>
</scm>
<dependencies>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
</dependency>
</dependencies>
</project>

Additional context The current POM resolves as the following, but Jitpack should be using Github API to add missing nodes.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<!--  do_not_remove: published-with-gradle-metadata  -->
<modelVersion>4.0.0</modelVersion>
<groupId>com.github.Zhuinden</groupId>
<artifactId>simple-stack</artifactId>
<version>2.8.0</version>
<packaging>aar</packaging>
<dependencies>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
</dependency>
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>3.0.2</version>
</dependency>
<dependency>
<groupId>com.github.Zhuinden</groupId>
<artifactId>state-bundle</artifactId>
<version>1.4.0</version>
</dependency>
</dependencies>
</project>

This is causing issues in certain people's CI.

https://github.com/cashapp/licensee/issues/133#issuecomment-1637984992

No changes have been made to build process between 2.7.0 and 2.8.0 on my side, therefore the changes must have happened on Jitpack side.

Please provide guidance or solution or fix to this issue, thanks.