A small question, can we upgrade proget but continue using classic maven for some time

@dean-houston Thanks

@dean-houston

https://repo1.maven.org/maven2/com/sun/activation/jakarta.activation/2.0.0-RC2/jakarta.activation-2.0.0-RC2.pom

Getting error for jakarta.activation-2.0.0 versions

Looks like there's some problem in orginal repo itself

Another example:
https://repo1.maven.org/maven2/com/sun/xml/bind/mvn/jaxb-parent/3.0.0/jaxb-parent-3.0.0.pom

I'm getting few of these errors.

An empty feed is getting this error

Getting this error while moving from classic maven to new maven on 2024.22

We've 3 proget servers in cluster, during upgrade do we have to stop all 3 servers and then do upgrade or can we do upgrade one server after another without stopping other servers.

Thanks

@dean-houston Thanks

Steps to reproduce:

1. Upgrade from 2024.13 to 2024.22
2. Upgrade classic maven feed to new maven feed
3. Revert back to classic maven feed
4. Downgrade from 2024.22 to 2024.13
5. Try accessing connectors page
   You'll get above error.

Could you pls look into it. If we've some problems and if we want to downgrade it's better if such issues doesn't occur.

Thanks

After renaming the feed the API keys are pointing to maven old feed. Should this be done manually. If so I think it's better if it's mentioned in documentation as well.

https://docs.inedo.com/docs/proget/feeds/maven#maven-classic-feed-types

Pls let us know your thoughts. If there are any such cases, pls let us know.