POM Configuration
The pom { } block inside publish { } configures the Maven POM metadata that is embedded in every published artifact. This metadata is required by Maven Central and used by dependency management tools to display project information. Kreate applies the same POM configuration to both the Maven Central and GitLab targets.
POM Structure
licenses { license { } }
Declares the license under which the library is distributed. Maven Central requires at least one license entry.
Property | Type | Description |
|---|---|---|
|
| Full license name, e.g. |
|
| URL to the license text |
|
| How the artifact is distributed; typically |
Common license values:
License | Name | URL |
|---|---|---|
Apache 2.0 |
|
|
MIT |
|
|
GPL 3.0 |
|
|
developers { developer { } }
Declares the people responsible for the project. At least one developer entry is expected by Maven Central.
Property | Type | Description |
|---|---|---|
|
| Unique identifier, e.g. a GitHub username |
|
| Full display name |
|
| Contact email address |
|
| Organization or company name |
|
| IANA timezone, e.g. |
All developer properties are optional. Kreate only sets those that are present — absent properties are simply omitted from the generated POM.
scm { }
The Source Control Management block describes where the source code lives. Maven Central requires SCM information for release artifacts.
Property | Type | Description |
|---|---|---|
|
| Web URL of the repository (e.g. GitHub page) |
|
| Read-only SCM URL: |
|
| Read-write SCM URL: |
For GitHub repositories, the standard values are:
issueManagement { }
Points consumers to where they can file bugs or feature requests.
Property | Type | Description |
|---|---|---|
|
| Name of the issue tracker, e.g. |
|
| Direct URL to the issue tracker |
ciManagement { }
Documents the CI system used to build and verify the project.
Property | Type | Description |
|---|---|---|
|
| Name of the CI system, e.g. |
|
| URL to the CI pipeline overview |
Both issueManagement and ciManagement are optional from Maven Central's perspective, but including them improves discoverability and transparency for library consumers.