How to change the maven feed disk path? Also Snapshot vs. Release Feeds?

I'm testing out the maven feed, and I noticed the disk path doesn't seem to be something I can update in the Proget UI.

For example, my maven feed's path is:

C:\ProgramData\ProGet\Packages.maven2\F9

and there doesn't seem to be a way to change it using the "Manage Feed" section.

Can this value be changed, so I can have this pointing to a separate disk location? If so, how?

Also I noticed there doesn't seem to be a distinction between snapshot and release feeds like you might find in other repo managers, like archiva, nexus, etc. That's probably OK, but I just wanted to know if that's correct? Or am I'm seeing side effects of using the free version of ProGet?

Thanks

Product: ProGet
Version: 3.7.1

There is a config setting that can be used to override the root storage location for maven feeds (changing C:\ProgramData\ProGet\Packages.maven2\ to somewhere else), but currently the path can't be overridden per-feed. Is this an important feature for you to have? We can always add it.

It's true that there is no distinction in the software between release/snapshot feeds. We're certainly open to feedback on this; we are pretty new to maven and I'm sure there's room for improvement in our initial support of it :) Anything you can tell us about how you'd use or like to use the maven support would help us improve.

I'd have to say that the ability to set the disk location is important for managing your repository. Fortunately, there's a way, but having that in the UI would be what I think most would expect. That would also make the feed comparable to the Nuget feed wrt this setting and actually it's a standard feature for maven repo managing in other repo managing tools.

For maven feeds - maven has the concept of snapshots, which are just builds between a release, and it's common in CI environments to save those in the repo with every build. That way you have those available to downstream components that depend on the upstream snapshot package for when downstream components build on different servers, physical locations, etc.

You can imagine that the builds pile up quickly, so it's convenient to separate those packages from the release packages. You then want a different retention policy for snapshots, because you generally don't need to keep more than a couple snapshots, while the releases need to persist forever.

Everything is fine in the pay-for versions of ProGet, because you can set the retention policies per feed and clean old snapshots, but that's not possible in the free version. Yes, you can do your own "under the hood" cleaning in that version, but retention/cleaning policies for release and snapshot repos/feeds are a standard feature in at least three different free versions of the maven repo managing software on the market that I'm aware of - and that makes snapshot cleaning a snap. Not so much with Proget - and for me, honestly, it makes it tougher to replace existing maven repo managers I have and push towards one tool in a mixed development environment where I have both maven and nuget needs (like I currently do).

Thanks

I see. Thanks for the feedback - I didn't think about retention but that is a very good point. Retention itself is also a relatively new feature for ProGet, and we are still evaluating whether it ought to be included in the free edition in some form.

Regarding feed-specific override paths, we probably will add this in a future release, but I can't give you a specific version as yet.