Maven Package Repository HTML Browsing à la Maven Central #12687

New Issue

GiteaMirror · 2025-11-02T10:18:09-06:00

GiteaMirror commented

2025-11-02 10:18:09 -06:00

Originally created by @JWT007 on GitHub (Mar 20, 2024).

Feature Description

I would like to request Gitea HTML Browsing for (at least) the Maven package type.

See https://repo1.maven.org/maven2/

Because (just my opinion) currently browsing the "tree" of uploaded packages is ... ummm how to say this... not nice.

It would be at least be useful to drill down through the hierarchical structure via HTML.

In addition, an alternative tool like NetBeans IDE Maven Repository Browser requires this "....//maven/.index" URL to work.
Personally I would rather have a tree navigation directly in Gitea (like Nexus and JFrog have) but as a workaround in the meantime, it would be useful if this would work.

Even better would to be also get full-fledged tree support in Gitea like here in Nexus, but that would be a different feature request. :)

Screenshots

No response

Originally created by @JWT007 on GitHub (Mar 20, 2024). ### Feature Description I would like to request Gitea HTML Browsing for (at least) the Maven package type. See https://repo1.maven.org/maven2/ <img width="865" alt="image" src="https://github.com/go-gitea/gitea/assets/28890586/69c41893-e8b5-45af-b5fe-49d6dbf73753"> Because (just my opinion) currently browsing the "tree" of uploaded packages is ... ummm how to say this... not nice. It would be at least be useful to drill down through the hierarchical structure via HTML. In addition, an alternative tool like NetBeans IDE Maven Repository Browser requires this "..../<owner>/maven/.index" URL to work. Personally I would rather have a tree navigation directly in Gitea (like Nexus and JFrog have) but as a workaround in the meantime, it would be useful if this would work. <img width="289" alt="image" src="https://github.com/go-gitea/gitea/assets/28890586/266281e5-d03e-4c62-834a-ef7c7b662574"> Even better would to be also get full-fledged tree support in Gitea like here in Nexus, but that would be a different feature request. :) <img width="431" alt="image" src="https://github.com/go-gitea/gitea/assets/28890586/f6793219-354b-4860-9ceb-9cdc5f86004e"> ### Screenshots _No response_

GiteaMirror added the topic/packages type/proposal labels 2025-11-02 10:18:09 -06:00

GiteaMirror commented

2025-11-02 10:18:10 -06:00

@KN4CK3R commented on GitHub (Mar 20, 2024):

I did not implement that because it's not needed for a working package registry.

"....//maven/.index"

That's proprietary from Nexus. Is there a documentation about the format?

@KN4CK3R commented on GitHub (Mar 20, 2024): I did not implement that because it's not needed for a working package registry. > "....//maven/.index" That's proprietary from Nexus. Is there a documentation about the format?

GiteaMirror commented

2025-11-02 10:18:10 -06:00

@JWT007 commented on GitHub (Mar 21, 2024):

Hi @KN4CK3R,

I have no idea to be honest.

I only found this: https://maven.apache.org/repository/central-index.html

Here is our situation, our Devops provider sort of shanghaied us with a sudden switch from Nexus to Gitea as a package manager for Maven (and other types). At the moment the only feature we are using from Gitea is package management (npm, maven, pypi, etc.).

However, we are missing some very useful features from Nexus - primarily:

the ability to view the structure in a tree and expand/collapse/delete nodes at a group level (ie. delete everything under "com.foo.bar").
the ability to upload third-party libraries via a UI (saw there was a PR for this but it is pending review)

These are very useful features for navigating a known GAV and primarily the only reason we needed the Nexus UI. It is helpful to check that artifacts are landing where they should or just cleaning out a bad build with many modules. Imagine a monolith Maven multi-module project with 30 artifacts :(. So the current Gitea - search for single artifact in specific version, click, click, click, delete package, confirm x30 is unfortunately less convenient.

@JWT007 commented on GitHub (Mar 21, 2024): Hi @KN4CK3R, I have no idea to be honest. I only found this: https://maven.apache.org/repository/central-index.html Here is our situation, our Devops provider sort of shanghaied us with a sudden switch from Nexus to Gitea as a package manager for Maven (and other types). At the moment the only feature we are using from Gitea is package management (npm, maven, pypi, etc.). However, we are missing some very useful features from Nexus - primarily: - the ability to view the structure in a tree and expand/collapse/delete nodes at a group level (ie. delete everything under "com.foo.bar"). - the ability to upload third-party libraries via a UI (saw there was a PR for this but it is pending review) These are very useful features for navigating a known GAV and primarily the only reason we needed the Nexus UI. It is helpful to check that artifacts are landing where they should or just cleaning out a bad build with many modules. Imagine a monolith Maven multi-module project with 30 artifacts :(. So the current Gitea - search for single artifact in specific version, click, click, click, delete package, confirm x30 is unfortunately less convenient.

GiteaMirror commented

2025-11-02 10:18:10 -06:00

@JWT007 commented on GitHub (Mar 21, 2024):

btw that was a typo above - it is just "/maven/.index" and the base URL "/maven" defaults to this page (i.e. instead of index.html).

@JWT007 commented on GitHub (Mar 21, 2024): btw that was a typo above - it is just "<URL>/maven/.index" and the base URL "<URL>/maven" defaults to this page (i.e. instead of index.html).

GiteaMirror commented

2025-11-02 10:18:10 -06:00

@JWT007 commented on GitHub (Mar 22, 2024):

@KN4CK3R

Found this as well:

https://jfrog.com/help/r/jfrog-artifactory-documentation/maven-indexer

Also the hint that IDEs like Netbeans and IntelliJ use these generated indexes for their integrations.

(I removed our internal servers and my user from the above image - to explain the blank gaps :) )

@JWT007 commented on GitHub (Mar 22, 2024): @KN4CK3R Found this as well: https://jfrog.com/help/r/jfrog-artifactory-documentation/maven-indexer Also the hint that IDEs like Netbeans and IntelliJ use these generated indexes for their integrations. <img width="979" alt="image" src="https://github.com/go-gitea/gitea/assets/28890586/0dd2d242-da4b-43e4-b403-c16c402a9a62"> (I removed our internal servers and my user from the above image - to explain the blank gaps :) )

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12687