You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Build failure: TypeFilter cannot be resolved to a type #534
Same on Linux, from want I can tell this is caused by a dependency change. Though then one has to ask themselves why the dependencies are not pinned to ensure reproducibility. This shouldn't be too much of a hassle but I'm not a Java dev so I might be wrong there. As a workaround you can comment of the right side of the if condition, so that the code looks like that:
Though then one has to ask themselves why the dependencies are not pinned to ensure reproducibility. This shouldn't be too much of a hassle but I'm not a Java dev so I might be wrong there.
My understanding is that version="0.0.0" means "use the latest version", which of course is not reproducible.
You're probable right, hope that this changes. While I can of course understand that that would create extra work, I still think its very important for a version to always build. A compromise maybe would be to only pin the dependencies for every release to ensure at least reproducibility there.
Activity
RedyCtl commentedon Feb 4, 2024
Same problem
Libadoxon commentedon Feb 5, 2024
Same on Linux, from want I can tell this is caused by a dependency change. Though then one has to ask themselves why the dependencies are not pinned to ensure reproducibility. This shouldn't be too much of a hassle but I'm not a Java dev so I might be wrong there. As a workaround you can comment of the right side of the if condition, so that the code looks like that:
This at least allows the package to build but probable unfixes the issues mentioned in the code (Jdtls 1212)
bsolar17 commentedon Feb 5, 2024
I think this is due to this file. E.g:
My understanding is that
version="0.0.0"means "use the latest version", which of course is not reproducible.Libadoxon commentedon Feb 5, 2024
You're probable right, hope that this changes. While I can of course understand that that would create extra work, I still think its very important for a version to always build. A compromise maybe would be to only pin the dependencies for every release to ensure at least reproducibility there.