I create a Maven Feed + Connector to https://repo1.maven.org/maven2

However, the feed is always empty. I ran FullMavenConnectorIndex and then BuildMavenFeedIndex but that didn't change anything.

There are no filters or vulnerability sources on the feed, so I expected to just see all available packages. We want to use this feed for caching, just as NPM (which works fine on the same server).

Am I missing something? How can I get the maven feed to work?

Product: ProGet
Version: 5.1.16

I know the theory behind the cached packages.

I looked into the Databse of ProGet, it appears to me that the "cached" status is simply a boolean field in the database.

Changings that seems to be effectively all that happens when you "Pull to ProGet" from the webinterface.

Unfortunately, I can't look into the ProGet source to confirm this, but evidence seems to be strong that all it is is a flag on the package version.

Is there a way to pull all currently "cached" packages to ProGet? I don't see any difference in the two states other than cached packages are removed when I clear the cache, so it doesn't seem like that action is doing much.

Product: ProGet
Version: 5.1.10

The following error occurrs when I try to run the Software Update Check on a fresh install of ProGet (Server 2016, IIS, SQL Express):

Checking for updates from inedo.com...
Error checking for updates: System.Net.WebException: Der Remoteserver hat einen Fehler zurückgegeben: (411) Länge erforderlich.
 bei System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
 bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
— Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde —
 bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 bei Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<GetUpdatesXmlAsync>d__3.MoveNext()
— Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde —
 bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 bei Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<ExecuteAsync>d__1.MoveNext()

Product: ProGet
Version: 5.1.9

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.

I set up a new npm feed in a fresh ProGet installation. When I set the npm registry to that feed and try to install any package, npm is stuck on the "readLocalPackageData" step and doesn't progress any further.

When I use the official registry, everything works fine. What is the cause of this?

Product: ProGet
Version: 5.1.9

I downloaded the Free Version of ProGet and activated it.

According to this the Free Version doesn't have Package Promition and Vulnerability Scanning.

But I can use both of these Features in my Free Version. Not that I'm complaining, but... is that in purpose?

Product: ProGet
Version: 4.7.13

I added a new maven feed + connector (to https://repo1.maven.org/maven2 )

Then I manually executed the Scheduled Tasks

1. FullMavenConnectorIndex
2. BuildMavenFeedIndex
3. FeedCleanup

All of them were successful, but the connector still shows up as "Unknown" state with 0 packages.

When I manually pull a package from the connector, it is correctly chached however.

What am I doing wrong? Why is the connector not showing as healthy and listing all packages it has?

Product: ProGet
Version: 4.6.6

I see. Yes, that returns the dependencies as well. Thanks for the hint. Although I would expect the other endpoint to also return them, maybe in a future version. Just for completeness sake.

With the two packages:

{
    "group": "test",
    "name": "Root",
    "version": "1.0.0"
}

{
    "group": "test",
    "name": "Dependent",
    "version": "1.0.0",
    "dependencies": ["test:Root"]
}

The JSON Response of

http://localhost:81/upack/upack/packages?name=Dependent&group=test

doesn't show the dependency

{
 "group":"test",
 "name":"Dependent",
 "latestVersion":"1.0.0",
 "downloads":"1",
 "isLocal":true,
 "isCached":false,
 "versions":["1.0.0"]
}

The website however, does.

Product: ProGet
Version: 4.5.4