Hi @atripp

Actually we created a license WTGBL and assigned it to a package that doesn't have any license. and the packages that have this license should be noncompliant.

So when we try to download it shouldn't we stop it without downloading even for first time.

And our team suggested that if some license type are only known after downloading full package, it would be possible to discard those without saving. Is this possible to do from your end?

Why this is needed:
Our security team told that there are few files on the machine that doesn't meet security standards. And few versions of this package shouldn't be available on the machine itself.

Thanks
Parthu

Previously we were able to block packages for specific version but now we don't see that option.

Why has this been removed?

Thanks
Parthu

Hi Team

We created a License WTGBL so that it blocks few log4j-core versions from being downloaded. But when we do that it's not stopping the package from being downloaded for the first time. After that it's blocked.

Proget version: 2024.13

Thanks

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