Open JackPGreen opened 5 months ago
It looks like in ZuluPrime#getAllPkgs
, it's hard coded to assume pkg.setPackageType(JDK)
.
I'd guess a simple solution would be something like pkg.setPackageType(filename.contains("jre") ? JRE : JDK)
as done elsewhere, but I'm not able to run the project to test this.
Will take a look at it, thx for reporting
Found 23 wrong packages and removed them, so they should be added with the next update run after the deployment will be done, so probably by tomorrow all packages should be back again with the correct package type.
@HanSolo this had been fixed but is happening again?
Darn...did another deployment yesterday and probably have a regression here...will take a look...thx for the heads up
Deployment is ongoing...should be fixed in around 2 hours (fingers crossed :))
Deployment is ongoing...should be fixed in around 2 hours (fingers crossed :))
Still showing 2 package results unfortunately.
Now this is interesting...on the staging and testing environment it doesn't show the wrong pkgs but on production it does...hmm...need to take a closer look why this happens
This is now showing one package - fixed or intermittent?
Take this request, which queries for
package_type=jdk
, but one of the results is:I.E. not a JDK, actually a JRE.
This looks to happen for other Zulu Prime versions as well.
Full request response: