helm goal configuration appends ${project.artifactId} to home and sources
See original GitHub issueDescription
Documentation says:
home: The Chart URL for this project’s home page, which is ${project.url} if not provided. sources: The Chart list of URLs to source code for this project, defaults to the list of ${project.scm.url} if not provided.
But reality is that home is set to: ${project.url}/${project.artifactId} and sources to ${project.scm.url}/${project.artifactId}
Info
- Eclipse JKube version : 1.0.0-rc-1
- Maven version (
mvn -v) : 3.6.3
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
steven-sheehy/helm-maven-plugin-1: Simple plugin to ... - GitHub
This is a Maven plugin for testing, packaging and uploading HELM charts. "HELM is a tool for managing Kubernetes charts. Charts are packages...
Read more >microbean-helm : 2.8.2.1.1.1 - Maven Central Repository Search
microBean Helm - Java bindings for the Helm API. ... Source code, https://github.com/microbean/${project.artifactId}/. Inception year, 2017 ...
Read more >Kubernetes Maven Plugin - JKube - Eclipse
This goal is for creating Helm charts for your Maven project so that you can ... values for home and sources will get...
Read more >Install Helm Charts Using This Maven Plugin - Austin Dewey
The helm:upgrade goal is invoked automatically during Maven's install lifecycle phase. This goal installs a Helm chart to Kubernetes or upgrades ...
Read more >Tutorial: Create, Build, and Deploy a Spring Boot Application ...
The goal of this tutorial is to create a simple Java Spring Boot application deployed in Kubernetes, using Helm charts.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

thanks @manusa for looking into this behaviour. Then it would be great to have some note about this (multi module project) in documentation.
I don’t particularly see this as a JKube specific bug.
Solution 1
The first and easiest fix would be to complete your helm configuration:
Solution 2
Maybe even with variables defined in the parent pom.xml
And configuration referencing those variables in
assembly/pom.xmlSolution 3
Configure inheritance for URL and SCM elements as stated in
MNG-6059(requires newer Maven versions):All of the provided solutions will output the following
Chart.yaml, just pick the one that suits you better 😉:See also