Maven indexes are for search only, and don't have any sort of sensible ordering, so you won't see packages like you would on npm feeds.

Behind the scenes, that's the only difference in how they're stored (and has been for as long as I remember); but I do know that data directly in the database is not officially supported. But for a one-off thing it's fine to do IMO

Hello Florian and Antoine, I've filed this as PG-1376.

The problem was our proxy. npm doesn't use the proxy exceptions that are configured in the system, so after updating them to include the ProGet server domain it works as expected.

Those features shouldn't be available in free versions; if so, that's an oversight/bug.

We'll add that as a proposed feature. I think the only issue aside from a small query/performance issue in implementation is that dependencies can change for different versions, so we'd really just be showing the latest version's dependencies there. Still, we are already doing that with certain fields like description, so that's not too bad...

That did the trick! Thanks for the hint.

Thanks for the bug report. We'll investigate and get a fix in the next release. We probably will also change the group syntax in dependencies to use a / instead of a colon, so you could just specify: "Root" (or "group/Root", etc). Of course, we would retain compatibility with the : syntax as well, but this would make things less ambiguous.

Hi Alana, the EventView helped. Thanks for the hint. An SQL Error was noting that the "EXECUTE" permission was missing for the Database-User of ProGet. Once I fixed that, everything runs smoothly now.