Skip to content

Add CLI argument for central content URL (central.content.url) #7989

@readonlyuser1

Description

@readonlyuser1

Is your feature request related to a problem? Please describe.
Currently, there is no CLI argument to override the central.content.url property. If you need to fetch artifacts from a custom Maven Central proxy or mirror, you can't configure the content URL via CLI — only the --centralUrl can be set.

Additionally, the default content URL, such as

https://search.maven.org/remotecontent?filepath=com/jolira/guice/3.0.0/guice-3.0.0.pom

may return an error

HTTP/2 502 
content-type: text/html
content-length: 150
date: Tue, 30 Sep 2025 11:23:50 GMT
server: nginx
x-cache: Error from cloudfront
via: 1.1 b0c7b942a33f0f4451718aee53f7840c.cloudfront.net (CloudFront)
x-amz-cf-pop: IAD12-P1
x-amz-cf-id: WD4kzXnixCmLCvWHyNm0DrVfr_sEi_Lv7kyvEIFVL-XbF75PXIcVPw==
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
strict-transport-security: max-age=31536000

which makes overriding this value from the CLI even more important for reliability and workarounds.

Describe the solution you'd like
Please add a dedicated CLI argument (for example, --centralContentUrl) to allow overriding the value of central.content.url directly from the command line, similar to how --centralUrl works. This would greatly improve flexibility for users working with private repository proxies or alternative content sources.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions