Closed lprimak closed 3 months ago
I just rebuilt and got the issue with Aspectj: RB_SHELL=1 ./rebuild.sh content/org/apache/shiro/shiro-2.0.1.buildspec
that is described in
https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/shiro/shiro-root-2.0.1.diffoscope
I suppose there is a subtle environment difference that triggers the output difference: let's try to figure out.
I'm on Linux, and my JDK 22 is OpenJDK 64-Bit Server VM Temurin-22.0.1+8
What is your precise env, please?
Hmmm... I just followed instructions on https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/doc/TOOLS.md
How did you manage to build with JDK 22? I had to do some tweaking. Maybe there is something I am missing?
short answer: I ran RB_SHELL=1 ./rebuild.sh content/org/apache/shiro/shiro-2.0.1.buildspec
longer answer: this run in interactive mode instead of container, and propose commands to copy/paste, relying on sdkman to switch JDK and Maven versions
I'll try your tweak for getting JDK 22 in container: yes, JDK 22 is a pain to inject because its Docker Hub image name conventions do not match previous ones notice: building releases with non-LTS should be avoided as much as possible, because the pain with getting non-LTS will grow with time
fixed by PR #187
I don't know why, but you're right, rebuild output is ok when done inside a container: previously, I rebuilt in interactive mode, and surprisingly, it does not give the same output
I suppose Aspectj has a fragility on environment, but I cannot really explain, but definitively nothing is random: tested both on Mac and Linux, both with Docker and Podman
for Shiro 2.0.1, now it is marked ok as we are able to rebuild consistently: rebuilding in interactive mode is just not ok, without much detail on why...
thanks for your efforts when reporting: it helped me improve JDK 22 support and container support, see #187 for details
Shiro 2.0.1 is indicating a reproducible build issue. However, when I run reproducible build locally, I cannot "reproduce" this issue, and there are no issue reported in the local RB build.
Also, There was another issue as I had to tweak the build files in order to run the build with JDK 22: